Calling LoadFromFile stream in
"bool Load(Event<Stream&> serialize, Stream& stream, int version){ ..."
calls user function "void XUserClass::Serialize(Stream& s){..." twice.
Once with backup.SetStoring(); flag and once with stream.SetLoading();.
Both are called from Core/Stream.cpp at 1287 in "bool Load(Event<Stream&> serialize, ...".

I don't think this is normal, since user callback is fired twice.

yes, i though it has something to do with it, but...


* maybe i am wrong - but i didn't notice anything about it in
** documentation(has a potential of 'unknown'/undetectable bugs) - personally i didn't know about it until i saw it in debugger.
** With that i mostly mean - app could get confused, "why is there IsStoring set if i am on start and only loading something"?
** I think i saw someone once asking about similar 'bug' about stream loading - 80% chance it was about this.
* when user is loading something, there is no need for 'backup yet(it could also be a read-only system on which this would probably fail in debug mode - on release it would go 'bug undetected')

If this can not be corrected(then 'new' documented feature is a must!!), how can one(in user callback) tell:
* if it is called from Load... by backup.Serialize with SetStoring flag set? (firing 1st time?)
* -||- but fired 2nd time - with SetLoading flag set?
* if is it really called from Load... if Storing is set?

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.

Func there is described perfectly!

It is of course not described(or pointed out) in LoadFromFile - that's why i newer saw it.

Ok, since it's not much away from LoadFromFile and on the same page,
there is no need to pointing that out.

Still, i don't recommend moving this to archive or delete,
since there may be others checking the same thing.