[Lazarus] Lazarus code editor improvement?

Joe Special at Joepgen.com
Sun Nov 3 13:31:21 CET 2019


Am 03.11.2019 um 08:25 schrieb Bo Berglund via lazarus:
> On Sat, 2 Nov 2019 17:46:09 +0100 (CET), Michael Van Canneyt via
> lazarus<lazarus at lists.lazarus-ide.org>  wrote:
>
>>> I myself had reported something similar with VNC, so it's indeed likely to
>>> be the culprit.
>> Yes. I've found Lazarus or any LCL app to be unworkable with VNC :(
> Yes, now that you mention it...
> I had a similar situation several years ago when I was using TightVNC
> on the RPi to access Lazarus. At that time nothing at all happened
> when I tried to enter the characters {[]}\|.
>
> So I created a text document with these chars and had it open when I
> programmed so I could go there and select-and copy the wanted char to
> be pasted into the editor.
> If I remember correctly it was ONLY the code editor that ill behaved,
> if I entered the characters into any other Lazarus window accepting
> strings as parameter it worked OK.
>
> And so it does now as well...
> For example the search box in Object Inspector is OK with these
> characters composed using the AltGr key.
>
> So now I have connected a monitor to my RPi4 and a spare TV keyboard
> with a mousepad to the RPi4 as well. When I use this to run a session
> the problem does not appear any longer...
>
> So indeed it is connected with VNC, but it also is connected with
> Lazarus' code editor window. It seems like this is the only affected
> window on the RPi, all others accept the composition key AltGr as part
> of entering a special char.
>
> I cannot use the direct connection, though, because I am heavily
> depending on being able to copy stuff across between the two systems
> and I also need to have access to my other tools on the Windows
> computer. So I have to stick with VNC anyway and work around the
> problem.
>
> And back again to Lazarus 2.0.6...
>
>

Please look at  issue 0030544 on https://bugs.freepascal.org. If I 
remember correctly, Mattias eventually found the reason and fixed it. 
Don't know why the problerm rearises...


More information about the lazarus mailing list