Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ Core » Stream Load serialization fired twice
Re: Stream Load serialization fired twice [message #61434 is a reply to message #61328] Tue, 11 February 2025 01:06 Go to previous messageGo to previous message
luoganda is currently offline  luoganda
Messages: 214
Registered: November 2016
Experienced Member
Functionality is a plus,
but - like i said - it just is not mentioned in the docs
and the app behaved a little weird - till i saw the "added bonus" in debuger,
since - depends how app is written(IsStoring/IsLoading may be used for some hokusPokus) - that
IsStoring/IsLoading may affect all later if/else/etc doings.

If app uses those two calls in Loading state of an app:
App must then not depend on that calls too much(once IsStoring will ret true and another IsLoading will also ret true),
so if app makes some hokus-pokus(mostly usually meaning app is not written correctly) - it must use it's own logic(it's own IsLoading/IsStoring).
That is not much of a problem though.

When user knows that there is a hidden backup(plus),
that makes a whole different story.

For upp this is mostly not a problem since source is there:),
but for closed-software that bonus not being mentioned could be an issue.

"(Actually, if you do not want the functionaly that Load provides, what is point of using it? Just create read stream and invoke Serialize)."
For convenience, instead of making 2/3lines - there is one.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Doubt with Buffer<> of a trivially destructible type
Next Topic: GetSmartTextSize() fails with QTF text
Goto Forum:
  


Current Time: Fri Jun 06 07:52:32 CEST 2025

Total time taken to generate the page: 0.03402 seconds