[Lazarus] Keys not recognized by Lazarus 1.6 code editor

[Bo Berglund]

On Wed, 24 Feb 2016 15:40:15 +0000, Graeme Geldenhuys
<mailinglists at geldenhuys.co.uk> wrote:

>On 2016-02-24 15:33, Bo Berglund wrote:
>> Or understand how the Raspbian desktop would land on the Win7 X
>> screen. :(
>
>As far as I know you do get a X Server implementation for Windows too.
>You would simply start that up, use Putty to SSH (with X11 port
>forwarding enabled) to the RPi, and run the Lazarus executable on the
>RPi. The Lazarus IDE should then appear on your Windows desktop.
>Obviously things like "File - Open..." will display the content on the
>RPi and not your Windows system - but that is normally desired anyway. ;-)
>
>At least the above is how it works between my X11 based systems.
>
>Regards,
>  - Graeme -

I found this tutorial on how to use XMing with RPi:
http://www.raspians.com/Knowledgebase/how-to-remote-desktop-with-xming-and-putty/

It is a bit roundabout, occupying the console connection via PuTTY,
but it did work to bring up some form of X window on my screen.
The displayed RPi desktop is very strange, though. Not at all the
Jessie desktop I am used to (example: black background and generally
strange looking). And it also seems like it decided that my keyboard
is a US layout, which is completely wrong of course.

When I launched Lazarus it shows up pretty well, but cannot be moved
inside the X window. And the X window itself cannot be moved on my
Win7 desktop either...
All-in-all it does not give me much improvement....

Now I have to figure out how to get it off of my Win7 desktop...
It does not act as any other Windows application does regarding the
windowing.
Shutting down the Putty session eventually removes the X window but it
is still present on my taskbar but won't maximize anymore.
Will have to use Task Manager.


Later:
I also tried the RDP solution linked to from the page above:
http://www.raspberrypiblog.com/2012/10/how-to-setup-remote-desktop-from.html

This does not have the unfamiliarities of the X-ming solution but
instead the key eating was present there too...
So the < and + keys could not be used.
So the exact same keys were affected in the same way, strange eh?

And the clipboard worked even worse than with TightVNC.

Seems like I will have to stick with TightVNC for the time being.

-- 
Bo Berglund
Developer in Sweden