Thank you both. Pity that messages / timeouts aren't individually settable. Perhaps my opinion will change over time. e.g. I would not have though I would want a SaveAs message to time out, as success / failure would probably be immediately important. OTOH, if you're doing SaveAs you're probably actively monitoring for any message anyways. Unlike autosaves that are working where it's nice that it happened but you don't want to interrupt your thought flow to acknowledge it by having to click close. (Perhaps this becomes automatic to click close, over time.)
OTOH - a successful save should fade out, but an unsuccessful one you probably want to pay attention to and not fade out. Hmmm. On Mar 21, 1:54 pm, PMario <[email protected]> wrote: > I use MessageFadeOut at the TeamWork place. > It works quite nice. > > http://hoster.peermore.com/recipes/TeamWork/tiddlers.wiki#MessageFadeOut On Mar 21, 12:58 pm, colmjude <[email protected]> wrote: > On Mar 21, 5:36 pm, "B. S." <[email protected]> wrote: > > You probably could do it via CSS, you could at least stop any message > popups appearing by targeting the messageArea element and using the > display: none CSS rule. Right, but that would be off / on (ignore / don't display), not fade. Probably not good as a general policy. > > So, for lack of a better understanding and way to ask the question: > > Can messageArea time out? > > You can do this using Paul's FadingMessagesPlugin. Using this you can > set a timeout which once it expires it will fade the message out. > You can get the plugin from the tiddlywiki svn > repositoryhttp://svn.tiddlywiki.org/Trunk/contributors/PaulDowney/plugins/Fadin... > > Hope that helps, It does, thank you. However, I got errors with it. I ended up googling and finding http://svn.tiddlywiki.org/Trunk/contributors/PaulDowney/plugins/WikifiedMessagesPlugin/WikifiedMessagesPlugin.js as well, at which point it got happy. Sadly, all messages are now prefixing with Å- (A-, where A has a circle on top) - with the installation of this last plugin. I guess this is a result of using a trunk source rather than some other linked / auto-update source. A quick peek at the code doesn't reveal an obvious fix to me (not that I would necessarily recognize it if it was staring me in the face). I don't see it obviously introducing a charset change, so am guessing there's a bug schmucking a pointer or string somewhere. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
