bizaro wrote:

>> 1. the initial line count was wrong (smaller that it should have
>> been). I thought it could be due to wrong
>> count of comment lines, but that turned out not to be the cause
>
> I think it skips empty lines. Maybe it could display line numbers with
> and without empty lines.

Yes, I did the math and it skips empty lines exactly.
Bruce, could you provide some sort of hook suitable for driving an external editor window to go to the
current line in the scriptdebug window? I don't know what the best interface would be, maybe a hook
command list that can then sendkeys to the editor window...

>
> Exec.ScriptDebug(0) has no effect if "PowerPro Script Debug" window is
> visible.

Could Exec.ScriptDebug(2) be made to restore the scriptdebug window on top if it's already open?

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.

;b! 8(exec.scriptdebug(-1))
toggles scriptdebugging

Would it make sense to add a generic ;e! to load expressions without breaking execution? Yes, if
conditional execution was possible...

if(condition)do
cmd1
;e! 8(exp1)
else
cmd2
;e! 8(exp2)
endif
;b!



Attention: PowerPro's Web site has moved: http://www.ppro.org



YAHOO! GROUPS LINKS




Reply via email to