thanks .. yes.. I was missing a cog. Many ways to perturb the rendered tab or its underlying live html (union CSS).
reload tab.. will fetch what is on record from server. The most obvious one. Will kill above 32 everywhere.
creating new chapter will also cause a refresh of some kind..
switching chapter....
and the missing one. changing position...
will the local internal data structure responsible for what we see on board, keep that user work... when going back and forth.
Excuse: I was working with empty boards as TOC (or to embed summaries of many positions without the clutter of the pieces (of wood)). So for me, the working memory context did not include the game thing, how restricted!
Are there other ways to lose the user drawing work? on the local side upon other user events?
REC and SYNC on or off. would that trigger a fetch server thing
thanks .. yes.. I was missing a cog. Many ways to perturb the rendered tab or its underlying live html (union CSS).
reload tab.. will fetch what is on record from server. The most obvious one. Will kill above 32 everywhere.
creating new chapter will also cause a refresh of some kind..
switching chapter....
> and the missing one. changing position...
will the local internal data structure responsible for what we see on board, keep that user work... when going back and forth.
Excuse: I was working with empty boards as TOC (or to embed summaries of many positions without the clutter of the pieces (of wood)). So for me, the working memory context did not include the game thing, how restricted!
Are there other ways to lose the user drawing work? on the local side upon other user events?
REC and SYNC on or off. would that trigger a fetch server thing