Can Console In/Output be modified?

[Curt Carpenter]

Using Lazarus 3.2 on Linux to debug a simple pascal program using the Console In/Output window.  Is there is a way to permanently turn off the "Always on top" mode for the console window?  Also: is there is a way to make the "Enter" keys on my keyboard all perform the same way (the Enter key on the numeric keypad has a different effect than the Enter on the qwerty portion of my keyboard.)? 

[MarkMLl]

Both those questions depend on the OS you're using.

In the case of unix many if not most window managers offer a "keep on top" or similar which can usually be applied to individual windows.

Enter key handling etc. will again depend on the OS and widget set, I don't know to what extent that's fixable or how amenable the LCL maintainers would be.

MarkMLl

[Martin_fr]

I don't think the window itself has that flag/option => but maybe its added by anchordockig?

[MarkMLl]

I don't think the window itself has that flag/option => but maybe its added by anchordockig?

No, it will be done (on unix) by the WM. See attached.

Updated: If Curt's talking about Windows, I think I remember that it had a way that an application program could add things to the system button. Could an IDE extension package add a "keep on top" facility?

Apologies for a fairly large screenshot, but KDE didn't want to action the PrintScreen key if the menus were already displayed.

MarkMLl

[Curt Carpenter]

OK thank you.  It took me a while to discover that the Enter key on the numeric part of my keyboard didn't work with the debugger's Console In/Output while the one on the qwerty part did.  Core problem though is that it's been a long time since I used the "small program" mode to do anything and don't have the right habits.   Great fun though! 

[MarkMLl]

If you're doing something interactive you'll be far better off using either "attach to program" or gdbserver for debugging.

The console window is very much for quick-and-dirty stuff, and its behaviour is to a large extent constrained by that of the backend debugger: hence the extra EOLs it inserts etc. plus a bit of a nightmare around UTF-8 output.

MarkMLl

[d2010]

If you're doing something interactive you'll be far better off using either "attach to program" or gdbserver for debugging.

The console window is very much for quick-and-dirty stuff, and its behaviour is to a large extent constrained by that of the backend debugger: hence the extra EOLs it inserts etc. plus a bit of a nightmare around UTF-8 output.

MarkMLl

My solution set Opacity-off-Crt overlay  MenuFrame is corect?
When I need debug& event , then I set  crt_opacity to 255.
is good solution?