DIAdem Idea Exchange

Hello,

1)

work would be much easier for me if direct debugging of Dialogs would be possible. It should be like debugging of scripts.

You set a breakpoint, let the script run and when it is paused you can look for the values of variables and continue in single steps.

Debugging with the Microsoft Script debugger is not really a comfortable solution.

2) The data type "variant" is great. But sometimes a type definition would help much (I'm used to define the type of variables, even from Visual Basic).

I would have the need for a "type" definition to combine several values to "one variable". With this construction a function could give some values in one result (e.g. a vector) and it would save some calculation time or global variables.

Example:

type rgbcolor

   dim r

   dim g

   dim b

end type

dim color as long

dim a as rgbcolor

a = conv_rgb(color)

msgbox a.r & "  " & a.g & "   " & a.b

function conv_rgb(col_long as long) as rgbcolor

    ...

end function

I've been spoiled by using other scripting environments lately, and thought I'd suggest a few features that I feel would make scripting in DIAdem a little more convenient:

• Check for un-dimmed variables when Option Explicit is turned on
• Check for unused dimmed variables (very helpful for cleanup)
• Check for variables that are used, but never initialized to a value

I feel these would be really useful for identifying and fixing bugs (especially for inexperienced script writers) and cleaning up old scripts, while not requiring major changes to the interface (although they could get really annoying if implemented incorrectly, may be difficult to implement in the back end, and may even require manual compilation to detect?).

Thanks!

-Josh