Roughly half the time when I get the RSOD, when I click on the offending tiddler to amend it, I get another RSOD telling me Node is not defined. I know that; I don't use it. I do my development in the browser. Why do I need to see this message, and more particularly, why is not having Node - I thought it was optional - so serious as to cause an RSOD?
Thanks, Andrew--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c31d7e18-23ac-4da1-b05c-9271f80e1445%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thanks Jeremy. It's a good idea to expain reason in messages. "As a result of an error, you need to restart Tiddlywiki to protect your data" would be more communicatively effective. Or if you feel "need to" is too coercive "should" conveys the notion of recommendation nicely. If you are uncomfortable addressing the user directly, then "Tiddlywiki should be restarted to protect its/your data" may suit. I prefer the more direct approach.
As i've noted elsewhere "This is embarrassing" is not useful. You have no need to be embarrassed on my behalf - or indeed, your own, in the rare event that the error originates in TW core.
The problem with being half clever (me) is that you make a lot of bad guesses. Sorry you have to suffer for them. The information "Node was not found" is really not useful to the casual user, so there's no value in presenting it. The user who can make use of it will easily find it in the console. (I would probably have been asking about it anyway, despite that)
Cheers.
On Thursday, 9 March 2017 22:14:58 UTC+11, Jeremy Ruston wrote:Hi AndrewThe “red screen of death” is triggered by untrapped JavaScript errors. In general, there are no guarantees as to the internal state of the system after an error because it will have been left in an intermediate state. That’s why the only good general advice is to restart TiddlyWiki. In practice, some errors are more recoverable than others, but continuing after an RSOD is inherently risky.Roughly half the time when I get the RSOD, when I click on the offending tiddler to amend it, I get another RSOD telling me Node is not defined. I know that; I don't use it. I do my development in the browser. Why do I need to see this message, and more particularly, why is not having Node - I thought it was optional - so serious as to cause an RSOD?The error message here is referring to a variable called “Node”, which is part of the standard DOM specification, and nothing to do with Node.js.Best wishesJeremy.Thanks, Andrew--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c31d7e18-23ac-4da1-b05c-9271f80e1445%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/e39c7db4-238b-42ec-87bd-ca56b21f65e4%40googlegroups.com.
As i've noted elsewhere "This is embarrassing" is not useful. You have no need to be embarrassed on my behalf - or indeed, your own, in the rare event that the error originates in TW core.I think I used that phrasing as a nod to a meme carried by Firefox and others (see below). I’d be happy to ditch it; it is a bit folksy for my tastes.
"We are sorry!" is better than "This is embarrassing", although I would omit both myself. I guess that depends on how often the RSOD is seen as a result of user activity, vs system bug appearance. Obviously in the latter case, if feels right to apologise. I prefer "To protect your data you need to restart TiddlyWiki". If we stick with "highly recommend", I prefer "restarting", but that may be Australian dialect.
The impact on me when I was first using TW of Red Messages: they got me in a hot sweat. Till I realised they are rarely fatal. My single biggest issue has never been them. Its been browser crashes corrupting the TW file.
To be honest its the AESTHETICS of the warnings as much as anything that scared me, and likely for others who have no clear idea what is happening.
TBH, I'd rather have a message like ...
DON'T PANIC.
There is a problem but it is likely not a disaster, just a small glitch.
To be safe, please close the window this TW is in and reopen it.
NOTA BENE: Please make sure that you always regularly backup your TiddlyWiki
because failures do happen & it would be a great shame if you lost your work.
... the target audience will be people who are at least willing to play with how tiddlywiki works.
... something in the direction of:
DON’T PANIC. There is a problem but it’s likely not a disaster.
TO BE SURE it is recommended you create a fresh backup of your TiddliWiki right now using your file explorer.
AFTER you did the backup, you can try to save this wiki.
AVOID DATA LOSS:
close and reopen this wiki now and check the content. If something is wrong, return to your last backups.