>>
>> Yes, I did the math and it skips empty lines exactly.
>
> I will try to fix.
thanks
>
> Since every editor is different, what I could do is say that if a
> command list OnScriptDebug exists, it will be run just before
> displaying dialog. (This command list would not be have debug
> display).
that sounds good. can you pass the contents of the scriptdebug window as arguments?
that is: line#, vector of edit box contents, vector of _expression_ values, dialog settings
>> Could ;b! be expanded to load expressions into the _expression_ edit
> boxes? Something like:
>>
>> ;b! 3(a*2) 4(1+1)
>> loads a*2 into the 3rd edit box and 1+1 into the 4th one.
>
> OK. Can also add
> ;b!if(expr)
> for conditional breakpoint.
excellent
>>
>> Would it make sense to add a generic ;e! to load expressions
> without breaking execution? Yes, if
>> conditional execution was possible...
>
> Not sure if you mean anything new by conditional expressions. I can
> add the ;e! but nothing would actually get displayed until next ;b!
> (or next single step).
Yes, that's what I had in mind
By conditional expressions I mean load edit boxes with ;e! based on program flow:
if(cond)do
;e! 1("in IF")
else
;e! 1("in ELSE")
endif
;b!
would load box 1 with "in IF" or "in ELSE" depending on the value of cond, as evaluated by normal
script flow. edit box 1 would be visible when program flow hits ;b!
> Also, ;e! would be processed if and only if script debugging is
> active.
ok
Attention: PowerPro's Web site has moved: http://www.ppro.org
YAHOO! GROUPS LINKS
- Visit your group "power-pro" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
