> It did not solve the Problem, [...]
Before I e-mailed my response I locally created a program that included
the function your posted. Double clicking the bottom field threw the
error you mentioned. After modifying the code as I described in my
previous post, the warning on the console
Hello Norbert,
thank you very much for your answer.
It did not solve the Problem, but it made me think about my string
handling in the callback function. The field throwing the error was the
input, not the output.
I just split the string using the pointer of the input and not copying
it before
> keybuf = gtk_entry_buffer_new ("Not yet generated", 45);
https://developer.gnome.org/gtk3/stable/GtkEntryBuffer.html#gtk-entry-buffer-new
The second parameter of gtk_entry_buffer_new() specifies the number of
characters in the string.
Either change 45 to 17 or to -1.
Best regards,
Norbert
Hello,
I just started developing GTK+ Applications.
But now I get the following error message and a broken Text when clicking back
in to the GTKEntry widget:
(gtk-keygen:18220): Pango-CRITICAL **: pango_layout_get_cursor_pos: assertion
'index >= 0 && index <= layout->leng
get the
following message at console :
Pango-CRITICAL **: pango_layout_get_cursor_pos: assertion `index = 0
index = layout-length' failed
The call back routine is doing nothing else that signaling a change to be
saved.
The effective change in the database is done on triggering
focus-out-event.
I
-CRITICAL **: pango_layout_get_cursor_pos: assertion `index= 0
index= layout-length' failed
The call back routine is doing nothing else that signaling a change to be
saved.
The effective change in the database is done on triggering
focus-out-event.
I am surely missing an obvious thing ...
What
