Haven't encountered the issues alluded to with the colon character in Chrome/Firefox.
I think the best way to avoid them, and possible the reason why I haven't encountered them, is to add 2 bookmarks containing javascript:startTrace() and javascript:stopTrace() respectively, I have such bookmarks in the bookmark toolbar of each of the browsers I have on my machine, making them readily accessible.
One important thing to realize, is that the .../Trace/All and .../Trace/Reset method is only really needed when having to debug asynchronous processing which is not directly caused by a user's client-side action, such as Timer activity and Callable Service requests. For processing which starts in user interaction using the Trace All method could be confusing, since there will usually be more than one trace file created, and the modeler will need to figure out which trace file is the relevant one.
And one more note ... The Startup-[timestamp] file is actually created automatically when the application server starts the specific application, and it's creation is not affected by the above options.
More information regarding visual debugging (tracing) can be found in http://www.tersus.com/#Id=46.
Regards,
David
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign
