On Tue, 23 May 2017, Salvatore Coppola via Lazarus wrote:
Hi to all the authors,
is in program a new edition of the guide?
Yes, but no date is set.
Michael.
--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
On 23.05.2017 20:43, Ondrej Pokorny via Lazarus wrote:
What are the equivalents for Qt, Qt5, Gtk2, Carbon, Cocoa?
I meaned - to use in _inside_ LCLIntf.SetForegrondWindow, not making new
LCL func.
--
Regards,
Alexey
--
___
Lazarus mailing list
On 2017-05-23 18:43, Ondrej Pokorny via Lazarus wrote:
What are the equivalents for Qt, Qt5, Gtk2, Carbon, Cocoa?
For anything running under X11 I have never had a problem with
XRaiseWindow(xapplication.display, FWinHandle);
So Qt and GTK could you that, if they aren't already.
Regards,
On 23.05.2017 19:38, Alexey via Lazarus wrote:
What do you think about using this rare API [beginning from WinXP] in
LCLIntf fnction? It will make LCL function work more stable: window
will always go to foreground. I used it in CudaText. It works.
What do you think about using this rare API [beginning from WinXP] in
LCLIntf fnction? It will make LCL function work more stable: window will
always go to foreground. I used it in CudaText. It works.
https://github.com/Alexey-T/CudaText/blob/master/app/fix_focus_window.pas
--
Regards,
Alexey
Hi to all the authors,
is in program a new edition of the guide?
--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus
Thanks, https://bugs.freepascal.org/view.php?id=31900
Please open an issue about it and I'll take a look on it.
zeljko
--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus
On 2017-05-23 14:27, kapibara via Lazarus wrote:
So the behaviour is inconsistent between platforms, and also
inconsistent within the same control (TListBox) depending on what item
is selected.
I believe I have reported that back in 2006 already. If not the same
component, then one of the
I find debugging value hints (TurboPowerIProDsgn installed, "Show value
hints while debugging") useful but annoying when the hint becomes so big
it covers the variable being checked or even fills the screen; on single
monitor systems the only way to close the hint is to scroll down to the
On 05/23/2017 04:15 AM, kapibara via Lazarus wrote:
Some more findings. Under Windows, the Edit.Exit event fires before both
SelectionChange and OnClick no matter what item you select.
It's normal. If you click onto listbox (OnMouseDown of listbox
triggers), TEdit looses focus and triggers
10 matches
Mail list logo