| On Tue, 07 Sep 2010 17:31:00 -0400, Steve Fbin <> wrote:
|
||| WAD. If you hover the mouse cursor (not the caret) over a
||| variable, the debugger will expand the variable and display it in
||| a tooltip.
||
|| Some of my variable functions execute a batch file to obtain
|| their result, a few execute external programs. When I debug a batch
|| program, the graphics pointer is usually hovering at some
|| uncontrolled, random location on the screen, thus possibly causing
|| serious side effects if a function with side effects happens to be
|| scrolled there. Could this artifact be enabled or disabled by the
|| user?
|
| It's totally inappropriate to have batch code executed while
| editing. @PING is a good example, but there are other more
| outrageous ones. What about @FILEOPEN, @FILEWRITE, @BALLOC,
| @CONSOLEB, a lot of numeric/string functions that depend on
| variables which might not even be defined (the list goes on).
| Evaluating many, many variable functions is akin to executing
| commands (and I hope you don't intend that hovering execute
| commands). I don't even think it would useful as an option!
On second thought I agree with Vince. In fact one of my problems with
debugging in the past was that files opened with @FILEOPEN were not closed
when quitting out put of the debugger in the middle of the batch program.
With the IDE running in a different environment this is no longer a problem,
though it has other issues. Since it became a separate process, I need to
manually switch to the directory where my .INI files are when I start IDE,
and specify the full path of the batch file to be debugged (usually by using
@SEARCH[]). I do wish if it cannot run in the instance of TCC whence invoked
it would at least run in one that is its child, and would thus automatically
inherit the parent's whole environment, since some batch programs may depend
on variables set by previously executed programs, possibly even history or
directory stack entries.
--
Steve