Re: [MSEide-MSEgui-talk] MSEide sometimes very slow

2019-04-22 Thread Fred van Stappen
Re-re @ Sieghard and Graeme. In project where threads are used, at init, I create a dummy thread to initialize threads. Otherwise it could have problems: type TDummyThread = Class(TThread) protected procedure execute; override; end; procedure TDummyThread.Execute; begin

Re: [MSEide-MSEgui-talk] MSEide sometimes very slow

2019-04-22 Thread Fred van Stappen
Re-@ Sieghard and Graeme: In mse README.TXT, at end: > ... > Press F9 and hope the best. ;-) > If there is a debugger timeout at startup enlarge the >'Project'-'Options'-'Target'-'Wait before connect' value. Maybe it could help? Fre;D De : Sieghard Envoyé :

Re: [MSEide-MSEgui-talk] msei18n vs PO files

2019-04-22 Thread Fred van Stappen
Hello Seighard. > I did download your special "po"-able version, but cannot use it at all, > because there's no source code for it. I didn't even find any source code > for a "po"-able version at all yet, even the latest git master archive > seems to not provide this ability. Huh, the po-able

Re: [MSEide-MSEgui-talk] MSEide sometimes very slow

2019-04-22 Thread Fred van Stappen
@ Seighard and Graeme: Do you have that behavior with previous mse release 4.6 ? https://sourceforge.net/projects/mseide-msegui/files/mseide-msegui/4.6/ De : Sieghard Envoyé : lundi 22 avril

Re: [MSEide-MSEgui-talk] Feature Request: double click select word in editor

2019-04-22 Thread Patrick Goupell
On 4/22/19 4:59 PM, Fred van Stappen wrote: Hello Patrick. > But don't try to do it all in one fix.  Break it down into individualchanges if possible. Not sure to understand, the fix was to change in sourcepage.pas, line 1255: if edit.isdblclicked(info.mouseeventinfopo^) and  

Re: [MSEide-MSEgui-talk] msei18n vs PO files

2019-04-22 Thread Sieghard
Sehr geehrter Herr van Stappen, Sie schrieben am Thu, 21 Mar 2019 23:40:21 +: > Hello Seighard. ie (never mind) Anyhow, after a really verry loong time, I got around to look through the current (mseide 4.6.2, the "stable" version) implementation of msei18n and adapt my old

Re: [MSEide-MSEgui-talk] MSEide sometimes very slow

2019-04-22 Thread Sieghard
Sehr geehrter Herr Geldenhuys, Sie schrieben am Mon, 22 Apr 2019 00:33:19 +0100: > I'm using the latest MSEide under Ubuntu 18.04 (64-bit) - compiled with > FPC 3.0.4 and GDB 8.1.0.20180409-git (what Ubuntu installed). > > Sometimes if I compile and debug my application, then MSEide slows down

Re: [MSEide-MSEgui-talk] Feature Request: double click select word in editor

2019-04-22 Thread Fred van Stappen
Re-hello. Maybe you ask to check if double-click-alone was used for something else? I do not think so, I did many check for ideU and it appears that all others double-click are used in conjunction of other key-press, like Ctrl, Shift. I did not found double-click-alone (without Shift or Ctrl)

Re: [MSEide-MSEgui-talk] Feature Request: double click select word in editor

2019-04-22 Thread Fred van Stappen
Hello Patrick. > But don't try to do it all in one fix. Break it down into individual changes > if possible. Not sure to understand, the fix was to change in sourcepage.pas, line 1255: if edit.isdblclicked(info.mouseeventinfopo^) and

Re: [MSEide-MSEgui-talk] Feature Request: double click select word in editor

2019-04-22 Thread Patrick Goupell
On 4/22/19 3:39 PM, Graeme Geldenhuys wrote: On 22/04/2019 20:09, fredvs wrote: So ok to change code? With or without {ifdef noshiftforselect}? I personally think the code and behaviour should change to conform with the standard behaviour seen in all other development tools and programmer

Re: [MSEide-MSEgui-talk] Feature Request: double click select word in editor

2019-04-22 Thread Fred van Stappen
Hello Graeme. OK, done in last commit 3929f5ce1. Fre;D De : Graeme Geldenhuys Envoyé : lundi 22 avril 2019 21:39 À : mseide-msegui-talk@lists.sourceforge.net Objet : Re: [MSEide-MSEgui-talk] Feature Request: double click select word in editor On 22/04/2019

Re: [MSEide-MSEgui-talk] Feature Request: double click select word in editor

2019-04-22 Thread Graeme Geldenhuys
On 22/04/2019 20:09, fredvs wrote: > So ok to change code? > With or without {ifdef noshiftforselect}? I personally think the code and behaviour should change to conform with the standard behaviour seen in all other development tools and programmer editors. I wouldn't bother with IFDEFs as that

Re: [MSEide-MSEgui-talk] BUG: trim trailing whitespace sometimes eats lineending during copy/paste action

2019-04-22 Thread Graeme Geldenhuys
On 22/04/2019 16:19, fredvs wrote: > Could you give a examples of sentences with lineended that cause the > problem? The the mailing list archive messages I listed below. > I am not sure that "Trim trailing whitespace on save" has something to do > with copy-paste, the method is called only at

Re: [MSEide-MSEgui-talk] BUG: trim trailing whitespace sometimes eats lineending during copy/paste action

2019-04-22 Thread Fred van Stappen
Hello Graeme. OK, I will study your post. Fre;D De : Graeme Geldenhuys Envoyé : lundi 22 avril 2019 21:09 À : mseide-msegui-talk@lists.sourceforge.net Objet : Re: [MSEide-MSEgui-talk] BUG: trim trailing whitespace sometimes eats lineending during copy/paste

Re: [MSEide-MSEgui-talk] Feature Request: double click select word in editor

2019-04-22 Thread fredvs
Hello Graeme. > Lazarus, Delphi, Eclipse, IntelliJ IDEA, Visual Studio etc all behave as Yes, I did try to convince Martin bu wihout luck. So ok to change code? With or without {ifdef noshiftforselect}? Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

Re: [MSEide-MSEgui-talk] MSEide sometimes very slow

2019-04-22 Thread Graeme Geldenhuys
On 22/04/2019 16:12, fredvs wrote: > In the case if you have installed ideU, > (https://github.com/fredvs/ideU/releases), do you have the same problem? > This because ideU uses a other process to load the debugger. Thanks for the suggestion - I'll test and let you know. Regards, Graeme --

Re: [MSEide-MSEgui-talk] Feature Request: double click select word in editor

2019-04-22 Thread Graeme Geldenhuys
On 22/04/2019 12:56, fredvs wrote: > The idea of Martin was to use 2xclick to jump to the declaration of > selection. I never understood why Martin did not standardise the behaviour like all other IDEs do. * double click a word in the editor selects the word * Ctrl+LClick navigates to the

Re: [MSEide-MSEgui-talk] Feature Request: double click select word in editor

2019-04-22 Thread Graeme Geldenhuys
On 22/04/2019 13:16, fredvs wrote: > It is a good idea to add the path of fpc, fpgui, external components, etc, > ---> all can be be "auto-jumped". Yes, I have been doing this for years with MSEide. :-) I have extensive project templates that I use, and use the Save/Load project options a LOT!

Re: [MSEide-MSEgui-talk] BUG: trim trailing whitespace sometimes eats lineending during copy/paste action

2019-04-22 Thread fredvs
Hello Graeme. Now that I am ready to jump into code, I cannot reproduce the problem. I did try with many copy/past but it is always ok. Could you give a examples of sentences with lineended that cause the problem? > If you have the Editor's "Trim trailing whitespace on save" setting > enabled

Re: [MSEide-MSEgui-talk] MSEide sometimes very slow

2019-04-22 Thread fredvs
Hello Graeme. Here on Debian 9.5 64 bit and GDB 8.1.0.2, I do not note some big delay. No more than delay to load the application in console with: $ gdb /the/program In the case if you have installed ideU, (https://github.com/fredvs/ideU/releases), do you have the same problem? This because

Re: [MSEide-MSEgui-talk] Feature Request: double click select word in editor

2019-04-22 Thread fredvs
> When you currently double click a word in the editor, it does nothing. To enable "auto-jumper" to declaration, you should add the search paths in "Project Options" "Debugger" "Source Directories". It is a good idea to add the path of fpc, fpgui, external components, etc, ---> all can be be

Re: [MSEide-MSEgui-talk] Feature Request: double click select word in editor

2019-04-22 Thread fredvs
Hello Graeme. About changing original behavior of mseide. What do you think to enable selection without shift key by "define" ? If you want selection without shift, add -dnoshiftedit. And in code: {$ifdef noshiftedit} // code without using shift key {$else} // code using shift key {$endif}