[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Bug in gtk 1.2.x (grab) (resent, no answer)
- From: Trever Adams <trever_Adams bigfoot com>
- To: gtk <gtk-app-devel-list redhat com>
- Subject: Bug in gtk 1.2.x (grab) (resent, no answer)
- Date: Wed, 23 Jun 1999 19:23:20 -0600
Below is a code fragment from a program I am porting from gtk 1.0.x to
1.2.x. If the grab_add and grab_remove are uncommented, the app locks
when it is called for doing RECORD_UPDATE, but not for RECORD_NEW. I
can comment out the ifs (the only bit of code that is at all different
for either call), and it still locks X hard until you kill the program
from another VC. If I comment the grab_Add and grab_remove, the
program seems to work wonderfully again. (This would make it totally
1.2.x safe and working, but with one visual snafu.) I can provide all
code in the path from gtk_main on to here if people are interested.
This is the same record_edit_form function I posted a few days ago,
except I finally was awake enough to get the ...add_with_viewport
function and put it to use. Scrolling now works as it should, save this
locks the app. Should I just leave out the grab stuff that is
commented, or is this proper code with odd results?
Trever Adams
if (record->type == RECORD_UPDATE) {
if (recordDefGetInitialValue(record, i)) {
gtk_entry_set_text(GTK_ENTRY(entries[i]),
recordDefGetInitialValue(record, i));
}
}
else if (record->type == RECORD_NEW)
gtk_entry_set_text(GTK_ENTRY(entries[i]), "");
}
gtk_widget_grab_focus(entries[1]);
/* gtk_grab_add(window); */
gtk_widget_show(window);
gtk_main();
/* gtk_grab_remove(window); */
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]