Re: Latest prerelease - <Control>1 crash
- From: Adam Krolnik <adam.krolnik@xxxxxxxxxxxxxxx>
- To: emelfm2@xxxxxxxxxxxxx
- Date: Tue, 07 Oct 2008 10:45:56 -0500
Okay, it doesn't crash any more.
Can you make a default action for files with an unknown file type ? Only
files without a suffix
or those with a categorized suffix get opened via the output.activate
option.
One other note; I tried to add a new category for file types. I added
the suffixes I wanted
and added a command. But the command was never kept. Each time I opened
the filetype configuration
window, there would be no command. I could add it and Apply. if I
switched to a new category and then
back to the new one, the command would be gone.
It does look good.
tpgww@xxxxxxxxxxx wrote:
On Mon, 06 Oct 2008 17:46:13 -0500
Adam Krolnik <adam.krolnik@xxxxxxxxxxxxxxx> wrote:
Here's with 1314.
This only occurrs when having <Control>1 be double click.
[DEBUG ] button binding cb begins: event-type: 4
[DEBUG ] button binding cb ends
[DEBUG ] _stroke_watcher_button_event_cb begins: event-type: 4
[DEBUG ] _stroke_watcher_button_event_cb, UNWATCHED PRESS
[DEBUG ] output button press cb
[DEBUG ] _stroke_watcher_button_event_cb begins: event-type: 7
[DEBUG ] current watch on widget
[DEBUG ] _stroke_watcher_button_event_cb, nothing to do
[DEBUG ] clear all gesture_watch's for a widget
[DEBUG ] button binding cb begins: event-type: 4
[DEBUG ] button binding cb ends
[DEBUG ] _stroke_watcher_button_event_cb begins: event-type: 4
[DEBUG ] _stroke_watcher_button_event_cb, UNWATCHED PRESS
[DEBUG ] output button press cb
Gtk-ERROR **: file gtktextview.c: line 5720
(gtk_text_view_start_selection_drag): assertion failed:
(text_view->selection_drag_handler == 0)
aborting...
That 'assert' is the symptom of a problem. I looked into gtk 2.6.9, in
gtk_text_view_start_selection_drag() it has:
g_return_if_fail (text_view->selection_drag_handler == 0);
In gtk 2.10.14 and 2.14.3 (sources of which I happen to have here) and
presumably all between these and maybe some before, there is only this:
if (text_view->selection_drag_handler != 0)
return;
Of course this begs the question - why the bad interactions with normal
'drag-selection' process for GtkTextView. I've changed a couple of things in
svn, maybe it will be better now.
Regards
Tom
--
Soli Deo Gloria
Adam Krolnik
Director of Design Verification
VeriSilicon Inc.
Plano TX. 75074
Co-author "Assertion-Based Design", "Creating Assertion-Based IP"
- Follow-Ups:
- Re: Latest prerelease - <Control>1 crash
- From: tpgww
- References:
- Latest prerelease - <Control>1 crash
- From: Adam Krolnik
- Re: Latest prerelease - <Control>1 crash
- From: tpgww
- Re: Latest prerelease - <Control>1 crash
- From: Adam Krolnik
- Re: Latest prerelease - <Control>1 crash
- From: tpgww
- Re: Latest prerelease - <Control>1 crash
- From: Adam Krolnik
- Re: Latest prerelease - <Control>1 crash
- From: tpgww
Other related posts:
- » Latest prerelease - <Control>1 crash
- » Re: Latest prerelease - <Control>1 crash
- » Re: Latest prerelease - <Control>1 crash
- » Re: Latest prerelease - <Control>1 crash
- » Re: Latest prerelease - <Control>1 crash
- » Re: Latest prerelease - <Control>1 crash
- » Re: Latest prerelease - <Control>1 crash
- » Re: Latest prerelease - <Control>1 crash
- » Re: Latest prerelease - <Control>1 crash
- » Re: Latest prerelease - <Control>1 crash
- » Re: Latest prerelease - <Control>1 crash
- » Re: Latest prerelease - <Control>1 crash
On Mon, 06 Oct 2008 17:46:13 -0500 Adam Krolnik <adam.krolnik@xxxxxxxxxxxxxxx> wrote:
Here's with 1314. This only occurrs when having <Control>1 be double click. [DEBUG ] button binding cb begins: event-type: 4 [DEBUG ] button binding cb ends [DEBUG ] _stroke_watcher_button_event_cb begins: event-type: 4 [DEBUG ] _stroke_watcher_button_event_cb, UNWATCHED PRESS [DEBUG ] output button press cb [DEBUG ] _stroke_watcher_button_event_cb begins: event-type: 7 [DEBUG ] current watch on widget [DEBUG ] _stroke_watcher_button_event_cb, nothing to do [DEBUG ] clear all gesture_watch's for a widget [DEBUG ] button binding cb begins: event-type: 4 [DEBUG ] button binding cb ends [DEBUG ] _stroke_watcher_button_event_cb begins: event-type: 4 [DEBUG ] _stroke_watcher_button_event_cb, UNWATCHED PRESS [DEBUG ] output button press cbGtk-ERROR **: file gtktextview.c: line 5720 (gtk_text_view_start_selection_drag): assertion failed: (text_view->selection_drag_handler == 0)aborting...
That 'assert' is the symptom of a problem. I looked into gtk 2.6.9, in
gtk_text_view_start_selection_drag() it has:
g_return_if_fail (text_view->selection_drag_handler == 0);
In gtk 2.10.14 and 2.14.3 (sources of which I happen to have here) and
presumably all between these and maybe some before, there is only this:
if (text_view->selection_drag_handler != 0)
return;
Of course this begs the question - why the bad interactions with normal
'drag-selection' process for GtkTextView. I've changed a couple of things in
svn, maybe it will be better now.
Regards
Tom
- Re: Latest prerelease - <Control>1 crash
- From: tpgww
- Latest prerelease - <Control>1 crash
- From: Adam Krolnik
- Re: Latest prerelease - <Control>1 crash
- From: tpgww
- Re: Latest prerelease - <Control>1 crash
- From: Adam Krolnik
- Re: Latest prerelease - <Control>1 crash
- From: tpgww
- Re: Latest prerelease - <Control>1 crash
- From: Adam Krolnik
- Re: Latest prerelease - <Control>1 crash
- From: tpgww