on 6/1/02 5:55 AM, Terry Vogelaar at [EMAIL PROTECTED] wrote: > I am kinda new to Revolution, so I could have overseen a feature allready > present in Revolution. Please notify me if that is the case. I think many of your requirements are indeed handled.
> - Ability to respond on AppleScript messages > (I use iListen speech recognition software; that relies on AppleScript) You can do this - see documentation for "appleEvent". > - Ability to execute AppleScript messages (I know it can be done with 'do') This works fine - not sure what more you'd want? > - Ability to connect via ADO with MS Access databases. Hmmm.... I think you can do this, via ODBC if not ADO: check out the Database Manager tool, and the documention for 'revdb_...' functions. > - In debug mode, it should be possible to 'step into', so I can see > where and how a handler or function is executed (like in HyperCard) As Geoff says, you can - use the 'step into' button. Did you mean 'step out of'? - I agree this is very confusing - it turns out most of the functionality is there; if you use the 'step into' button on the final statement of a handler or function, then the debugger continues back to the handler or function that called it, whereas 'step over' doesn't. This is inconsistent with most debuggers. In effect, these buttons are mislabelled: they really mean 'break at the next statement in any handler' (step into) and 'break at the next statement in this handler' (step over). This confused me as well. It would still be more convenient if there was a function which mean 'break at the next statement not in this handler' (ie 'step out of' as it is understood by most debuggers). > - It should be possible to mark a line of script so I can enter the > debug mode any time; not only when an error is reported. Sometimes > a script does not contain errors that the environment is aware of, > put still the results are not what they should be. As Geoff said, you can mark a line of script in the script debugger (the equivalent of setting the checkmark in HyperCard, and like that, not preserved through launches of Revolution). You can also add a statement in the script, "breakpoint". This is the equivalent of "debug breakpoint" in HyperCard, and is preserved across launches of Revolution (and because it is a statement, you can make it conditional). In both cases, unlike HyperCard, the breakpoint will only take effect if you have the debugger open; I think this can be viewed as a feature, in effect allowing you to switch off debugging (but I'm not entirely convinced). There is also an issue about the accuracy of the script displayed in the debugger. In general, Revolution would greatly benefit from having a topic in the documentation devoted to debugging. I'm sure Jeanne will get to it eventually! I think it's also an area which would benefit from some additional work by the development team. But most of what you wanted is possible, if not necessarily optimal. Ben Rubinstein | Email: [EMAIL PROTECTED] Cognitive Applications Ltd | Phone: +44 (0)1273-821600 http://www.cogapp.com | Fax : +44 (0)1273-728866 _______________________________________________ improve-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/improve-revolution
