Ciao PMario
Before I reply on your suggested message (I need think about it a little
bit first)... I'd like to make an observation ...
I think one of the reasons its not so easy to get the message exactly right
is awareness that users are likely, unfortunately, NOT routinely
backing-up. So
On Thursday, March 16, 2017 at 1:45:53 PM UTC+1, @TiddlyTweeter wrote:
>
> 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
Ciao all
Just a side comment of my experience as a user who doesn't really know what
those messages mean other than "close it & restart." :-)
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
That's my experience too. I've never seen it when it wasn't my fault.
That's why I feel the apology is awkward, because mainly it will be the
user at fault. The communication is well-intentioned, but it doesn't match
the pragmatics of the situation. That kind of mismatch is what I was
looking
On Wednesday, March 15, 2017 at 11:03:52 AM UTC+1, tejjyid wrote:
>
> "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
"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
On Saturday, March 11, 2017 at 9:05:14 AM UTC+1, Jeremy Ruston wrote:
>
> 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
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
Still a subscriber, but haven’t posted in a long time. I need help with
something not TW related, but that I thought this group might have a thought
about.
The email from Jeremy was in my mailbox this morning, but the “to” address was
not mine. It was "h...@alph146.prodigy.net.” There were
Hi Andrew
The “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.
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
11 matches
Mail list logo
