Re: [gtk-vnc-devel] gtk-vnc trouble

[Gerd Hoffmann <kraxel redhat com>]

Daniel P. Berrange wrote:
>> Number one and most annonying is the i18n keyboard problem.  My app used
>> to simply send us keysyms unconditionally.  Hackish, agreed.  Worked
>> reasonable well though, with the exception of keys not presend on us
>> keyboards.  Doesn't work any more as the keyboard handling is now in the
>> widget source ...
> 
> Not sure what you mean by  'send keysyms unconditionally' ? Do you need an
> API for injecting fake keysyms to the widget ? 

No.  I had a hard-coded table "keycode -> us-map keysym" and used that
to send us keysyms to the vnc server no matter what keyboard mapping the
client machine has.

>> Next problem is that the vnc_display_set_*_grab() functions seem to have
>> no effect.  Any hints on that one?
> 
> They ought to be working - the gvncviewer demo program uses them to control
> whether pointer grab occurs or not. The default is not to grab pointer or
> keyboard. Setting grab pointer, implies grab keyboard. It'll grab upon first
> pointer press. If merely doing keyboard grab it grab keyboard on mouse enter
> and ungrab on mouse leave of the widget.

I see it grab all the time and vnc_display_set_*_grab(widget, FALSE)
doesn't turn it off.

>> Also vnc_display_open(), vnc_display_close(), then again
>> vnc_display_open() with the same widget instance doesn't work.
> 
> Do you call the  vnc_display_close & vnc_display_open  immediately following
> each other, or does the mainloop run ? The close function does an asynchronous 
> shutdown so the GTK mainloop needs to run before it'll actually die off. 

mainloop runs inbetween due to user interaction being needed (there is a
"connect ..." menu entry).

cheers,
  Gerd