In general, what do you do when something goes wrong. On several occasions, I've written some code (an action to be performed when something happens) but I see nothing - I expect some output but there is none.
A typical case is an incorrect filter which returns nothing but I'd expected it to return something - the trouble is that I don't know it's the filter that has failed it might be something else. I don't know where or how to start debugging. If it were C or JS I'd just start adding print statements at appropriate places printing out variables I guess I'd like a <$log ....> widget that did something like console.log(...) in Javascript or printf in C -- just to know my code has been run. I don't know how the code that evaluates a widget works - if a widget "fails" (meaning that it breaks some rules of well-formed or something) I seem to get a silent error (meaning that there is no output) It would be nice to have some kind of error tiddler - that logged silent errors - so I could read it when debugging. Do any of these things (logs, error tracing, etc.) exist? Is there a tutorial on "How to debug a faulty TW program?" Cheers /Joe On Wednesday, 9 January 2019 11:53:08 UTC+1, PMario wrote: > > hi, > the dumpvariables macro may be an option > > https://tiddlywiki.com/#dumpvariables%20Macro > > -m > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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 https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/9702af66-804e-48ff-baa2-17cc9116128d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
