Thanks, take your time, no rush. The '$:/state/' works as expected, the wiki no longer prompts the user for saving on every page refresh, which is great. That further exposes the weird behavior though, now it only truly randomizes the field on page refresh via startup actions, or through the button on the $:/state/ tiddler. All other buttons generate one single number. If you edit that tiddler the number generated changes once until page is refreshed or the tiddler edited.
Anyway, for now it works where it matters which is on page load. Many thanks for your help :) On Sunday, 15 March 2015 02:22:00 UTC, Jed Carty wrote: > > As far as the weird non-random behavior I hadn't run into it before. It > seems to be writing to the field, but it always picks the same number. > There shouldn't be any limitation like that, it works as expected in all > the other tests I have tried. I will look into it. It is a straightforward > use of the built in javascript random number generator. There may be some > conditions where the rng isn't actually random. I will look into it later. > > To prevent the wiki from wanting to save you should have the field being > changed in a tiddler with a name starting with '$:/state/' or '$:/temp/', > tiddlers with names that start with either of those don't trigger the > saving reminder stuff. > > For people who know javascript: > I really doubt it is the problem, but is there any problem in the > prerelease that would affect the rng? or conditions where the rng would > always return the same value? -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
