[Evolution-hackers] [Old Version 2.28] Tasks: Prevent Ctrl-X in search box to accidentally delete tasks.
I don't know if this works cleanly in the newest versions. But in my
ancient version, doing a search by entering a term in the search box,
selecting a piece of text of that search string and hitting Ctrl-x would
result in the currently selected task to be deleted. And Ctrl-v would
not bring it back. I inserted a little crutch in my old version to
simply disable the cut command and that worked. See attached diff.
--
thomas
commit cf5444ce2def9c51d40ee6bf4091ad8c516f1a8b
Author: Thomas Mittelstaedt
Date: Fri Aug 16 22:21:47 2013 +0200
Just a quick fix: Disable the TasksCut command in order not accidentally
delete tasks while hitting Ctrl-x in the search text box.
diff --git a/calendar/gui/tasks-control.c b/calendar/gui/tasks-control.c
index a788931..b24b9a6 100644
--- a/calendar/gui/tasks-control.c
+++ b/calendar/gui/tasks-control.c
@@ -269,7 +269,8 @@ tasks_control_focus_changed (GtkWidget *widget,
GdkEventFocus *event, struct foc
static BonoboUIVerb verbs [] = {
BONOBO_UI_VERB ("TasksOpenTask", tasks_control_open_task_cmd),
BONOBO_UI_VERB ("TasksNewTask", tasks_control_new_task_cmd),
- BONOBO_UI_VERB ("TasksCut", tasks_control_cut_cmd),
+ /* BONOBO_UI_VERB ("TasksCut", tasks_control_cut_cmd), */
+ BONOBO_UI_VERB ("TasksCut", NULL),
BONOBO_UI_VERB ("TasksCopy", tasks_control_copy_cmd),
BONOBO_UI_VERB ("TasksPaste", tasks_control_paste_cmd),
BONOBO_UI_VERB ("TasksDelete", tasks_control_delete_cmd),
___
evolution-hackers mailing list
evolution-hackers@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] crash in 3.8.2
On Thu, 2013-08-15 at 11:35 -0500, André Saunite wrote: > I think it has to do with the Intel video card. > > I have a machine with an integrated intel card and a nvidia card, with > nvidia evolution starts normally, but after I upgraded the kernel and > logged in using the intel card I had this problem, after switching > back to nvidia it worked normally again. Hi, I'm sorry, but what problem? (You said "this problem".) I'm afraid that without a backtrace it's quite hard to guess anything from "crash in 3.8.2"). Furthermore, if change of the card (driver) helps, then the issue might be out of evolution itself. I saw some video freeze on gnome-shell, but I was told that it works fine when using other than gnome-shell desktop (if I recall correctly). Anyway, please use bugzilla for this kind of issue, and paste the backtrace of the crash there as well, thus there'll something one can look on. Thanks and bye, Milan ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers
[Evolution-hackers] crash in 3.8.2
Hi, I think it has to do with the Intel video card. I have a machine with an integrated intel card and a nvidia card, with nvidia evolution starts normally, but after I upgraded the kernel and logged in using the intel card I had this problem, after switching back to nvidia it worked normally again. BR André Saunite ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] alarm-notify patch: Proposed changes to notify dialog
On Thu, 2013-08-15 at 07:47 +0200, Thomas Mittelstaedt wrote: > I made a couple of changes to my ancient (2.28.4) version of evolution. > First, I encountered a nuisance in the alarm notify dialog, that when > the dialog pops up and a new alarm is coming in, the selection changes > to this new item, while the user potentially ist just clicking the > dismiss or snooze button. I made the attached change to simply not > preselect anything, having checked that the same is still running in the > current git version at https://git.gnome.org/browse/evolution. Hi, I made a little change to your proposal, and committed it as: https://git.gnome.org/browse/evolution/commit/?id=daaf089be7ea1ac97a39ce6e38696be6851d3259 > I also had a crash in the alarm-notify app and I inserted the attached > safety check. I guess you face: https://bugzilla.gnome.org/show_bug.cgi?id=641711 but I cannot tell for sure without a backtrace. I cannot speak for the "ask before dismiss all" right now, I do not have any strong opinion on it. The other clients do not ask too, which doesn't mean it's a bad idea to add the confirmation dialog. By the way, it's better to file bugs, as it's kind of a tracker and things do not get lost there, like on mailing lists. See: https://bugzilla.gnome.org/enter_bug.cgi?product=Evolution Bye, Milan ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers
