rconn
Administrator
- May
- 13,637
- 253
Staff member
The "Display folding margin" option is not remembered.
WAD (because there's no conceivable benefit in turning it off permanently).
By registering with us, you'll be able to discuss, share and private message with other members of our community.
SignUp Now!The "Display folding margin" option is not remembered.
> X-ing the console has always been a very convenient way to stop
> everything, including IDE.
> As for those messages from Windows, they're unsightly. I don't want to
> see them and I have always figured you didn't want them, even when users
> do dumb things.
> So IDE is attaching to its parent's console, running the batch file and
> processing console I/O ... right?
> I don't see a need for IDE to keep giving itself focus when running to
> end or breakpoint. Debugging may involve console input, in which case
> having to switch to the console every time is a pain, and if the console
> won't keep focus long enough to accept input, it's impossible.
On Wed, 08 Sep 2010 00:03:03 -0400, rconn <> wrote:
|---Quote---
A simple test shows that if the user X's the console after a GUI app has
attached to the console, the GUI app is terminated.
> I'm not talking about stepping. If your running to end or breakpoint,
> everything in the debugger is happening so fast that you can't tell
> anything
> except that it's flying around a loop. And the debugger can update its
> window without having focus.
On Wed, 08 Sep 2010 08:23:49 -0400, rconn <> wrote:
I see (but why?). I can't even run another app (browser/email/et c.) while IDE is doing that. I'm surprised Windows lets you how focus like that and I
certainly don't like it.
theparent TCC> On Tue, 07 Sep 2010 23:02:28 -0400, rconn <> wrote:
>
> |---Quote (Originally by vefatica)---
> |And putting "EXIT" is a BTM and running/debugging in IDE causes IDE
> to exit (and not TCC).
> |---End Quote---
> |
> |Right -- so?
> |
> |You're presumably invoking the IDE from a stand-alone TCC session.
> The EXIT will terminate the IDE session running the batch file; it
> doesn't have any effect on the parent TCC.EXE that launched IDE.
> (Did you *want* it to kill the parent session?)
>
> No, that was just an experiment, and I was wrongly thinking that
> was running the batch file.
>
>
>
>
its> ---Quote---
> > I'm not talking about stepping. If your running to end or breakpoint,
> > everything in the debugger is happening so fast that you can't tell
> > anything
> > except that it's flying around a loop. And the debugger can update
focus.> > window without having focus.
> ---End Quote---
> The debugger cannot highlight the current line without getting the
>
> Rex Conn
> JP Software
>
>
>
>
I see (but why?). I can't even run another app (browser/email/et c.) while IDE is doing that. I'm surprised Windows lets you how focus like that and I
certainly don't like it.
But if you are executing to end or to breakpoint, there is no "current line." There is only a current line when the script is paused - i.e. single step or breakpoint.
On Wed, 08 Sep 2010 12:04:41 -0400, rconn <> wrote:
|Windows will not let you do that -- unless you've specifically modified a registry entry to allow it (which you apparently have done).
Yes I have done that. And now I appreciate Microsoft's intention more. Grabbing
focus can be rude; IDE's version of it is downright obnoxious.
> Yes I have done that. And now I appreciate Microsoft's intention more.
> Grabbing focus can be rude; IDE's version of it is downright obnoxious.
> There's little to be gained from that highlighting when running freely.
> It'd be fine with me if IDE only highlighted when it was debugging and
> paused or ar a break.
> So it is with BDEBUGGER. We *expect* that when we debug a batch
> script, that TCC is actually executing and we are debugging the
> script which is executing in TCC. The reality is completely
> different however.
> I don't see a need for IDE to keep giving itself focus when running to
> end or breakpoint.
> A simple test shows that if the user X's the console after a GUI app
> has attached to the console, the GUI app is terminated.