Hello Seighard.
> So, I think the best way to handle this would be to simply exchange the
> beviours each condition trigger and so avoid any possible collisions.
Yes, it is what was done in last commit.
Fre;D
--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/
Sehr geehrter Herr Geldenhuys,
Sie schrieben am Tue, 23 Apr 2019 18:05:39 +0100:
> In MSEide double click is consequently used for window navigation. In
> source editor double click shows the breakpoints window if there is a
...
> So it seems to have a behaviour assigned, ONLY if a breakpoint
On 22/04/2019 00:43, Graeme Geldenhuys wrote:
> When you currently double click a word in the editor, it does nothing.
Thanks Fred. I tested with the latest MSEide and it works perfectly now. :)
Regards,
Graeme
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
> I remember having a discussion about this a long time ago. I quick
> search revealed the following info from Martin.
https://www.mail-archive.com/mseide-msegui-talk@lists.sourceforge.net/msg09612.html
Ooops, yes, of course I remember too now.
And so, fake news, there is one 2xclick still
On 22/04/2019 22:10, Fred van Stappen wrote:
> 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) used by mseide.
I remember having
On 22/04/2019 21:15, Patrick Goupell wrote:
> But don't try to do it all in one fix. Break it down into individual
> changes if possible.
Good point - makes for much easier regression testing too.
Regards,
Graeme
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
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
) used by mseide.
Fre;D
De : Patrick Goupell
Envoyé : lundi 22 avril 2019 22:15
À : mseide-msegui-talk@lists.sourceforge.net
Objet : Re: [MSEide-MSEgui-talk] Feature Request: double click select word in
editor
On 4/22/19 3:39 PM, Graeme Geldenhuys wrote:
> On
2:15
À : mseide-msegui-talk@lists.sourceforge.net
Objet : Re: [MSEide-MSEgui-talk] Feature Request: double click select word in
editor
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}?
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
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
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
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/
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
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!
> 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
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}
01:43
À : mseide-msegui
Objet : [MSEide-MSEgui-talk] Feature Request: double click select word in editor
When you currently double click a word in the editor, it does nothing.
All other editors will select the word you double clicked. With MSEide
you need to hold down SHIFT while you double click
When you currently double click a word in the editor, it does nothing.
All other editors will select the word you double clicked. With MSEide
you need to hold down SHIFT while you double click to get the same
behaviour, which is a bit annoying.
Regards,
Graeme
--
fpGUI Toolkit - a
19 matches
Mail list logo
