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

[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
   FreeOnTerminate:=True;
   Terminate;
end;


And in mainform.oncreate:

 TDummyThread.Create(false);


Maybe do this for mseide too?

OK, I stop, I do not have other ideas.

Fre;D


De : Fred van Stappen 
Envoyé : mardi 23 avril 2019 01:25
À : General list for MSEide+MSEgui
Objet : Re: [MSEide-MSEgui-talk] MSEide sometimes very slow

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é : lundi 22 avril 2019 23:38
À : mseide-msegui-talk@lists.sourceforge.net
Objet : Re: [MSEide-MSEgui-talk] MSEide sometimes very slow

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
> drastically. eg pressing Ctrl+F9 takes about 3-5 seconds before I start
> seeing compiler output in the Messages window. If I quit and restart the
> IDE, then it works fine for a while and I see instant compiler messages.
>
> Anybody else experiencing this issue?

Yes, same here. Using mseide-msegui 4.6.2, fpc 3.0.2 ([2018/05/11] for
x86_64) and gdb 8.2.1 under Slackware Linux with kernel 4.19.30.
Usually, restarting the debugger helps out in it, afterwards it reacts
normally again. But it seems to happen also on normal compiles, which
should not even need the debugger at all, still, reloading it removes the
issue.

--
--
(Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung
nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem)
---
Mit freundlichen Grüßen, S. Schicktanz
---




___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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é : lundi 22 avril 2019 23:38
À : mseide-msegui-talk@lists.sourceforge.net
Objet : Re: [MSEide-MSEgui-talk] MSEide sometimes very slow

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
> drastically. eg pressing Ctrl+F9 takes about 3-5 seconds before I start
> seeing compiler output in the Messages window. If I quit and restart the
> IDE, then it works fine for a while and I see instant compiler messages.
>
> Anybody else experiencing this issue?

Yes, same here. Using mseide-msegui 4.6.2, fpc 3.0.2 ([2018/05/11] for
x86_64) and gdb 8.2.1 under Slackware Linux with kernel 4.19.30.
Usually, restarting the debugger helps out in it, afterwards it reacts
normally again. But it seems to happen also on normal compiles, which
should not even need the debugger at all, still, reloading it removes the
issue.

--
--
(Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung
nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem)
---
Mit freundlichen Grüßen, S. Schicktanz
---




___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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 version was transfered here:
https://github.com/fredvs/mseide-msegui

In mse-org/mseide-msegui is the original no-po-able version.

> , I did get some smallish projects working in the meantime someone might be 
> interested in.

Yes, with pleasure.

>Otherwise, I wish you good luck with the continuation of Martin's heritage
> and hope it will prosper and be of use to many future projects.

If you still give your advices/help mse will be very prosper.

Thanks Seighard.
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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 2019 23:38
À : mseide-msegui-talk@lists.sourceforge.net
Objet : Re: [MSEide-MSEgui-talk] MSEide sometimes very slow

> Sometimes if I compile and debug my application, then MSEide slows down
> drastically. eg pressing Ctrl+F9 takes about 3-5 seconds before I start
> seeing compiler output in the Messages window. If I quit and restart the
> IDE, then it works fine for a while and I see instant compiler messages.
>
> Anybody else experiencing this issue?

Yes, same here. Using mseide-msegui 4.6.2, fpc 3.0.2 ([2018/05/11] for
x86_64) and gdb 8.2.1 under Slackware Linux with kernel 4.19.30.
Usually, restarting the debugger helps out in it, afterwards it reacts
normally again. But it seems to happen also on normal compiles, which
should not even need the debugger at all, still, reloading it removes the
issue.

--
--
(Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung
nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem)
---
Mit freundlichen Grüßen, S. Schicktanz
---




___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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
 (info.mouseeventinfopo^.shiftstate*[ss_double,ss_shift,ss_left] =
       [ss_double,ss_shift,ss_left]) then begin

With that:

if edit.isdblclicked(info.mouseeventinfopo^) then begin

How to do this in individual changes?

Fre;D

I meant if there were other non standard key combinations (like the 
double-click on a word) Martin used.


If there are no others then nothing else to worry about.

___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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 "scripting" extensions to that. They make msei18n not really
scriptable, as it still presents it's GUI, but they allow it to be command
line controlled and to process a previously prepared project without further
manual interaction, i.e. generate a new set of translation libraries, e.g.
for a modified version.
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.
So I have to ask where this is and how I could get at it. Downloading an
offically accessible git archive isn't a problem, but as I couldn't find
one, it looks like there are just distributed patches lying around
somewhere that I have no information of, or the source is not officially
accessible to everyone.
BTW, I did get some smallish projects working in the meantime someone might
be interested in. These are
- a stand alone file requester to be used for shell scripts  (as already
  mentioned)
- a calculation unit / component for numerical entry fields, featuring
  chain computation and respecting operator precedence, and along with it,
  a similarly enhanced keypad dialog component for use with touch screens
- a simple utility to test and display key codes, names and characters
  (strings) as produced by key presses.

I could provide zip archives of any of these projects, hopefully containing
everything needed to reproduce them within the realm of a working mseide
environment (i.e. that means it does NOT comprise mseide-msegui).
In the case of msei18n, I could also produce a unix standard diff patch to
apply to the original utility source code.

The extensions implemented for msei18n are in short:

- new command line switches
 '--process': the "scripting" function
 '--target', a provision to modify the fpc compiler used, e.g. to compile
 for i386 on a x64 machine, or to cross compile for windows on linux, and
 '--version', an additional provision for selecting the compiler by
 appending a postfix to its name, e.g. a version number or such.

- processing functions
  The processing functions are passed as a string parameter to the
  "--process" switch. They are shortly described in the source file
  "main.pas" along with the definition of the processing function
  "ExecuteCommands". The process parameter may comprise any number of
  functions and their pertaining parameters as following:

 Syntax of --process switch:

 --process=(,)”

 command:
make(:)|
open(:)|
saveas(:)|
import(:)|
export(:)|
new(:)|
exit

  For more details, please refer to the commentary in the source file.
  All the functions are named according to the respective menu entries.

Please give a notice if you think any or some of the above mentioned items
might be of interest to you or the project and whether and what I should do
about them.

Otherwise, I wish you good luck with the continuation of Martin's heritage
and hope it will prosper and be of use to many future projects.

-- 
-- 
(Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung
nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem)
---
Mit freundlichen Grüßen, S. Schicktanz
---




___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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
> drastically. eg pressing Ctrl+F9 takes about 3-5 seconds before I start
> seeing compiler output in the Messages window. If I quit and restart the
> IDE, then it works fine for a while and I see instant compiler messages.
> 
> Anybody else experiencing this issue?

Yes, same here. Using mseide-msegui 4.6.2, fpc 3.0.2 ([2018/05/11] for
x86_64) and gdb 8.2.1 under Slackware Linux with kernel 4.19.30.
Usually, restarting the debugger helps out in it, afterwards it reacts
normally again. But it seems to happen also on normal compiles, which
should not even need the debugger at all, still, reloading it removes the
issue.

-- 
-- 
(Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung
nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem)
---
Mit freundlichen Grüßen, S. Schicktanz
---




___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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) 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 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 will simply
> confuse the code more than anything else.
>

I would agree.

Standardize to what all other editors do.  Try to identify any other non
standard actions Martin has.

But don't try to do it all in one fix.  Break it down into individual
changes if possible.

Patrick




___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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
   (info.mouseeventinfopo^.shiftstate*[ss_double,ss_shift,ss_left] =
 [ss_double,ss_shift,ss_left]) then begin

With that:

if edit.isdblclicked(info.mouseeventinfopo^) then begin

How to do this in individual changes?

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 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 will simply
> confuse the code more than anything else.
>

I would agree.

Standardize to what all other editors do.  Try to identify any other non
standard actions Martin has.

But don't try to do it all in one fix.  Break it down into individual
changes if possible.

Patrick




___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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 editors. I wouldn't bother with IFDEFs as that will simply
confuse the code more than anything else.



I would agree.

Standardize to what all other editors do.  Try to identify any other non 
standard actions Martin has.


But don't try to do it all in one fix.  Break it down into individual 
changes if possible.


Patrick




___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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 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 will simply
confuse the code more than anything else.


Regards,
  Graeme

--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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 will simply
confuse the code more than anything else.


Regards,
  Graeme

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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 save-file.

Martin suggested the link between the two. Note this was reported back
in 2015 and I still experience the paste issue every time I use MSEide.
If simply grown to ignore it and manually fix the pasted code.

Please read the full message threads of each link.

https://www.mail-archive.com/mseide-msegui-talk@lists.sourceforge.net/msg08917.html

https://www.mail-archive.com/mseide-msegui-talk%40lists.sourceforge.net/msg08839.html


Regards,
  Graeme

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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 action

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 save-file.

Martin suggested the link between the two. Note this was reported back
in 2015 and I still experience the paste issue every time I use MSEide.
If simply grown to ignore it and manually fix the pasted code.

Please read the full message threads of each link.

https://www.mail-archive.com/mseide-msegui-talk@lists.sourceforge.net/msg08917.html

https://www.mail-archive.com/mseide-msegui-talk%40lists.sourceforge.net/msg08839.html


Regards,
  Graeme

--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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 declaration

Lazarus, Delphi, Eclipse, IntelliJ IDEA, Visual Studio etc all behave as
above.

MSEide not.


Regards,
  Graeme

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

My public PGP key:  http://tinyurl.com/graeme-pgp


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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!


Regards,
  Graeme


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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 and you copy and paste multiple lines of code

I am not sure that "Trim trailing whitespace on save" has something to do
with copy-paste, the method is called only at save-file.

Fre;D




--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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 ideU uses a other process to load the debugger.

Fre;D 



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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 "auto-jumped".

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

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

[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}

The idea of Martin was to use 2xclick to jump to the declaration of
selection.

I prefer to do the reverse (see ideU)  2xclick+shift to jump to the
declaration of selection.
And 2xclick alone to select a word (or line if re-2xclick).

So, to resume, option or not?

Fre;D









--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk