On Fri, 2006-03-03 at 10:01 -0400, ext Antonio Gomes wrote:
Hi there,
back to virtual keyboard stuff, I'm wondering how could a non-gtk
entry (mozilla password html form in this case) could hide the inputed
text (after showing for a short period of time - default behaviour),
like if I set
On 3/6/06, Tommi Komulainen
[EMAIL PROTECTED] wrote:
On Fri, 2006-03-03 at 10:01 -0400, ext Antonio Gomes wrote: Hi there, back to virtual keyboard stuff, I'm wondering how could a non-gtk entry (mozilla password html form in this case) could hide the inputed
text (after showing for a short
Hi there,back to virtual keyboard stuff, I'm wondering how could a non-gtk entry (mozilla password html form in this case) could hide the inputed text (after showing for a short period of time - default behaviour), like if I set gtk_entry_set_visibility of a GtkEntry to FALSE. I've been looking
Some keys are not recognized, though. Actually, mainly those related to deleting actions (like delete, backspace virtual keyboard keys and so on). As far as I can see/understand, xterm also had to handle them in a proper way, using vte [1] for that. Is it ? Is there other GtkIMContext singal to
hi Aaron,I didn't mention this in my last e-mail, but you'll also need to setup a
signal handler for the GtkIMContext object's commit signal.I have it (the 'commit' signal) already connected and also its callback defined as it is in your post at
On 1/18/06, Aaron Levinson [EMAIL PROTECTED] wrote:Hi Aaron,
One possibility is to use gdk_window_foreign_new() to wrap the nativewindow in a GdkWindow object.Maybe I can jump this first step, once I already have a GtkWidget the wraps mozilla guts the make easier called GtkMozEmbed, provided by
You can use gtk_im_context_show() to force the window for a GtkIMContext
object to be displayed. This function isn't mentioned in the
documentation for the class, but it is in the include file. An example of
using this function can be found in the osso-xterm code.
Aaron
On Fri, 20 Jan 2006,
I have to admit that I don't understand why you would need to use this
specialized function in your case. The situation with osso-xterm is a
specialized one, since the GtkIMContext object's window needs to be
activated as the result of a menu action. In your case, however, you
already have a
One possibility is to use gdk_window_foreign_new() to wrap the native
window in a GdkWindow object. Then, after creating a GtkIMMulticontext,
you could try using gtk_im_context_set_client_window() with the new
GdkWindow object. You'll want to listen for key-press and key-release
signals (hard to
