/ Forums / Advansys Formativ / Formativ Creator / Debugging option in Studio/Admin

  • Creator
    Topic
  • #3571
    GoumJer
    Participant

    Hello,

    is there something like a debugger in Studio 2.0, like there is available in VB. (step in code, read variables, jump to sub/function etc.)?

    Would make programming/debugging a lot easier.

    Thanks,

    Jeroen

  • Author
    Replies
  • #5472
    Support 1a
    Participant

    Dear Jeroen,

    Thank you for your question above. Unfortunately Formativ 2.0 does not provide step debugging facilities you describe. Including step debugging facilities for Formativ (which runs inside the GroupWise process) is a non-trival task. Nonethess, we know this is an important feature and has been slated for a future release.

    In the meantime, you can use other techniques to approximate step debugging. Perhaps the most useful is to include trace output commands in your Applet, then use any debug output viewer capable of intercepting calls to the Win32 OutputDebugString() function.

    Through the use of strategically-placed trace commands, you can get a real-time picture of the execution of your Applet. Trace commands are created through the use of the Utilities.Trace() method. Utilities.Trace() takes a single string argument. The string value you supply is output to any attached debugger in real time as the Applet executes.

    Utilities.Trace() ultimately uses the Win32 function OutputDebugString() to output the string value. This function sends a string to the debugger for display. If GroupWise has no debugger attached, the system debugger displays the string. If GroupWise has no debugger and the system debugger is not active, OutputDebugString() does nothing. If you use the SysInternals DebugView utility, you only need to run DebugView prior to starting GroupWise – you do not need to attach it to the GroupWise process.

    We use and recommend the free DebugView utility from SysInternals: http://www.sysinternals.com/ntw2k/freeware/debugview.shtml

    I hope this helps.

    Advansys Support

    #5473
    GoumJer
    Participant

    Oke, debugger works. Gives a reasonable help.

    Next question:

    where can I find a list of the objects available?

    i.e.
    Set Msg = Context.Clientstate.CommandMessage
    strSubject=msg.subject

    What other objects are available besides subject?

    Regards,

    Jeroen

    #5471
    Support 1a
    Participant

    The Client argument is documented in the Developers Guide. It is a native GroupWise Client object. Here’s some information from the Developers Guide, which also contains a link to online documentation:

    Client: This argument represents the state of the GroupWise client at the time your applet was executed. It is the same as the GroupWise C3PO ClientState Object. Your applet should not assume a specific Client object is in a particular state. Rather, the ClientName, MajorVersion, and MinorVersion properties should be checked to identify the appropriate state of the object. Full documentation of the Client argument can be found at: http://developer.novell.com/ndk/doc/gwc3po/gwc3penu/data/hye3ji8g.html

    All other objects are documented in the Language Guide. In terms of the message store access object you mention, search for ‘composingitem’ and ‘account’ in the index.

    I hope this helps.

    Advansys Support

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.