[Lazarus] First click disappearing
Hi, I'm completely puzzled by the following bug: My setup: trunk lazarus, FPC 3.1.1, GTK2 widgetset. in the FPReport report designer the first click almost anywhere is simply not registered in any OnMouseDown handler. I have tried to reproduce this in a more simple program, but failed till now. Stephano (patspi...@gmail.com) can reliably reproduce this as well, and reported that he has observed the same problem for some time in the source editor of the lazarus IDE as well, but it disappeared after some weeks (presumably something was fixed) The strange thing is that it can be reproduced in the dialogs of the program, as well, not just in the main window. To reproduce: * compile the reportdesign program (components/fpreport/design) using FPC 3.1.1. * Start program * Load design attached to bug 33453 (any other will do as well) * click on a field -> nothing happens. (onmousedown is not called, I debugged this) * click again on the field -> field is selected See also https://bugs.freepascal.org/view.php?id=33453 and the 2 related bugs. Michael. -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
[Lazarus] TP-like nested comment handling
I am playing with some old code which assumes TP-like handling of nested comments: i.e. there is only one level of nested comments, the first comment limiter closes a comment. However, Lazarus handles comments like FPC: it counts the nesting level and does syntax highlighting accordingly. Is there any option I am missing so I get correct syntax highlighting for TP-like nested comment handling? -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
[Lazarus] TP-like nested comment handling
I am playing with some old code which assumes TP-like handling of nested comments: i.e. there is only one level of nested comments, the first comment limiter closes a comment. However, Lazarus handles comments like FPC: it counts the nesting level and does syntax highlighting accordingly. Is there any option I am missing so I get correct syntax highlighting for TP-like nested comment handling? -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
[Lazarus] Changes to bugreport #33331 completely changes long standing behaviour
Dear List. The bug report: https://bugs.freepascal.org/view.php?id=1 has completely changed the behavious of how TTreeview behave! The old behaviour (sending OLD current node in OnChanging, sending NEW/SELECTED node in OnChange) is consistent across other components as well. The bug report is closed so i cannot make an objection to this "fix". It has created a heck loads of bug in our programs due to this change - can this please be reverted?!? Kind regards, Torsten Bonde Christiansen -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
[Lazarus] TP-like nested comment handling
I am playing with some old code which assumes TP-like handling of nested comments: i.e. there is only one level of nested comments, the first comment limiter closes a comment. However, Lazarus handles comments like FPC: it counts the nesting level and does syntax highlighting accordingly. Is there any option I am missing so I get correct syntax highlighting for TP-like nested comment handling? -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
[Lazarus] Test
please disregard this message -Torsten -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] Changes to bugreport #33331 completely changes long standing behaviour
03.04.2018 11:52, Torsten Bonde Christiansen via Lazarus пишет: > Dear List. > > The bug report: https://bugs.freepascal.org/view.php?id=1 > > has completely changed the behavious of how TTreeview behave! > > The old behaviour (sending OLD current node in OnChanging, sending > NEW/SELECTED node in OnChange) is consistent across other components as > well. > > The bug report is closed so i cannot make an objection to this "fix". > > It has created a heck loads of bug in our programs due to this change - > can this please be reverted?!? I reopened this bug report. Please comment there. -- Best regards, Maxim Ganetsky mailto:gan...@narod.ru -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] Changes to bugreport #33331 completely changes long standing behaviour
On 2018-04-03 14:41, Maxim Ganetsky via Lazarus wrote: 03.04.2018 11:52, Torsten Bonde Christiansen via Lazarus пишет: Dear List. The bug report: https://bugs.freepascal.org/view.php?id=1 has completely changed the behavious of how TTreeview behave! The old behaviour (sending OLD current node in OnChanging, sending NEW/SELECTED node in OnChange) is consistent across other components as well. The bug report is closed so i cannot make an objection to this "fix". It has created a heck loads of bug in our programs due to this change - can this please be reverted?!? I reopened this bug report. Please comment there. Thank you Maxim! -Torsten. -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] TP-like nested comment handling
On Sun, 1 Apr 2018 19:37:13 +0200 Florian Klaempfl via Lazarus wrote: > I am playing with some old code which assumes TP-like handling of nested > comments: i.e. there is only one level of nested comments, the first > comment limiter closes a comment. However, Lazarus handles comments like > FPC: it counts the nesting level and does syntax highlighting > accordingly. Is there any option I am missing so I get correct syntax > highlighting for TP-like nested comment handling? Here this is highlighted and parsed correctly: {$mode tp} { { } begin end. How do you tell Lazarus that the unit is tp mode? Mattias -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] A fix for an annoying problem on Linux
On 04/02/2018 09:51 AM, Anthony Walter via Lazarus wrote: Here you go ... what did you change? i see the code you added but i do not see any difference in the pictures you posted... -- NOTE: No off-list assistance is given without prior approval. *Please keep mailing list traffic on the list unless* *a signed and pre-paid contract is in effect with us.* -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] A fix for an annoying problem on Linux
On Tue, 3 Apr 2018, wkitty42--- via Lazarus wrote: On 04/02/2018 09:51 AM, Anthony Walter via Lazarus wrote: Here you go ... what did you change? i see the code you added but i do not see any difference in the pictures you posted... The value for the dropdown in the property editor has now a surrounding rectangle. I also had to look really carefully to see it. Michael. -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] A fix for an annoying problem on Linux
Op 03-04-2018 15:40 schreef wkitty42--- via Lazarus: On 04/02/2018 09:51 AM, Anthony Walter via Lazarus wrote: Here you go ... what did you change? i see the code you added but i do not see any difference in the pictures you posted... It's a very (very) subtle difference... It will add the focus-line at the top and bottom within the edit. (in this case in red but depends on color-scheme) Rik -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] A fix for an annoying problem on Linux
On 4/3/2018 6:51 AM, Rik van Kekem via Lazarus wrote: Op 03-04-2018 15:40 schreef wkitty42--- via Lazarus: On 04/02/2018 09:51 AM, Anthony Walter via Lazarus wrote: Here you go ... what did you change? i see the code you added but i do not see any difference in the pictures you posted... It's a very (very) subtle difference... It will add the focus-line at the top and bottom within the edit. (in this case in red but depends on color-scheme) Well, would have really helped if the OP mentioned that with one simple sentence. I did not see that either until looking again after Michael mentioned it... :( Ralf --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] TP-like nested comment handling
Am 03.04.2018 um 15:02 schrieb Mattias Gaertner via Lazarus: > On Sun, 1 Apr 2018 19:37:13 +0200 > Florian Klaempfl via Lazarus wrote: > >> I am playing with some old code which assumes TP-like handling of nested >> comments: i.e. there is only one level of nested comments, the first >> comment limiter closes a comment. However, Lazarus handles comments like >> FPC: it counts the nesting level and does syntax highlighting >> accordingly. Is there any option I am missing so I get correct syntax >> highlighting for TP-like nested comment handling? > > Here this is highlighted and parsed correctly: > > {$mode tp}> { { } > begin > end. > > How do you tell Lazarus that the unit is tp mode? Well, only in the Project options because I didn't want to modify the source, this is why I asked how to switch the behavior (I found out I can do this by changing the highlighter to delphi). BTW: {$mode iso/extpas} do not change the behavior either, only $mode tp does. -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus