Hi Mark, I've had a look at your stack, and I see that it simply a method to switch on this undocumented feature that already exists in Rev. My stack does the same as this existing feature - only my method does not waste so much hard disk space, and will produce a new log file every time Rev is restarted (so that if the same sequence of events causes the crash then the log files that were last modified at the times of the crashes should all end the same way).
I'm glad to know my work hasn't a complete waste of time. I do think it should be an engine-level feature, and should probably adopt a more concise logging format. If there is any interest in this let me know and I'll put my stack online. Bernard On Mon, Sep 29, 2008 at 1:26 PM, Bernard Devlin <[EMAIL PROTECTED]> wrote: > Hi Mark, > > I don't know. Before I built my own utility, I mentioned the need for > something like this several times (on the improve list and in comments on > RQCC). No-one referred me to yours. Can it log changes to properties (such > as setting the name of a stack), and calls to in-built functions? If it > can't do that, then I think there is still a need for what I've suggested. > Mind you, I use your errorLib all the time, so if someone can do it outside > the engine, I'm sure you can. > > I've just found it your stack. I didn't know there was anything called > revVerboseDebug. It isn't listed in the dictionary of either 2.9 or 3.0. > > So it certainly looks like your logging stack will do more, so I probably > wasted another day. > > Bernard > > _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
