aboutsummaryrefslogtreecommitdiffstats
path: root/e-util/e-alert.c
Commit message (Collapse)AuthorAgeFilesLines
* Don't crash on missing EAlert definitions.Matthew Barnes2011-04-131-0/+1
|
* EAlertBar: Make warnings time out after 5 minutesMatthew Barnes2011-03-261-4/+44
| | | | | | Warnings are generally meant for transient errors. No need to leave them up indefinitely. Close them automatically if the user hasn't responded after a reasonable period of time has elapsed.
* Coding style and whitespace cleanup.Matthew Barnes2011-03-061-7/+20
|
* Bug #614480 - Avoid using G_TYPE_INSTANCE_GET_PRIVATE repeatedlyMilan Crha2011-02-251-7/+3
|
* Remove NULL checks for GObject methods.Matthew Barnes2011-02-131-2/+2
| | | | | As of GLib 2.28 all GObject virtual methods, including constructed(), are safe to chain up to unconditionally. Remove unnecessary checks.
* Coding style and whitespace cleanup.Matthew Barnes2011-01-301-2/+2
|
* Disconnect signal handlers from actions in alert_dispose()Milan Crha2010-12-211-2/+7
|
* Free/busy meeting view doesn't work due to non-working extensionMilan Crha2010-12-061-0/+3
|
* Pass an EAlertSink to e_alert_sink_submit_alert().Matthew Barnes2010-11-011-5/+5
| | | | | | | Passing a random GtkWidget and then searching its ancestors for an EAlertSink turned out to be not as useful as I thought. Most of the time we know about and have access to the widget that implements EAlertSink, so just pass it directly as an EAlertSink.
* Send errors to an EAlertSink instead of the task bar.Matthew Barnes2010-10-191-1/+0
| | | | | | This marks the end of unintrusive error dialogs, which were too unintrusive. We now show errors directly in the main window using the EAlert / EAlertSink framework.
* EAlert: Allow arbitrary actions to be added.Matthew Barnes2010-10-191-21/+139
| | | | | | | | | | | | | | You can now amend the predefined actions in an EAlert by calling e_alert_add_action(). Useful for adding actions from an existing GtkUIManager. Call e_alert_peek_actions() to obtain a combined list of predefined and custom actions. These will typically serve as "related" actions for GtkButtons (cf. gtk_activatable_set_related_action()). Also, both EShellWindow and EShellView now implement EAlertSink. Use EShellWindow for application-wide alerts, EShellView for view-specific alerts.
* Composer: Show cancellable operations and errors inline.Matthew Barnes2010-10-131-61/+83
| | | | | | | | | | | | | | | 'Send' and 'Save Draft' are now asynchronous and run outside of Evolution's MailMsg infrastructure. Add an EActivityBar to the composer window so these asynchronous operations can be tracked and cancelled even in the absense of a main window. Also add an EAlertBar to the composer window so error messages can be shown directly in the window. Instead of calling e_alert_dialog_run_for_args(), call e_alert_submit() and pass the EMsgComposer as the widget argument. The EMsgComposer will decide whether to show an EAlertDialog or use the EAlertBar, depending on the GtkMessageType of the alert.
* Coding style and whitespace cleanup.Matthew Barnes2010-10-041-1/+0
|
* Messin around with EAlerts.Matthew Barnes2010-09-301-240/+355
| | | | | | | | | | | | | | | | | | | Trying out a new interface called EAlertSink. The idea is to centralize how errors are shown to the user. A GtkWindow subclass would implement the EAlertSink interface, which consists of a single method: void (*submit_alert) (EAlertSink *alert_sink, EAlert *alert); The subclass has complete control over what to do with the EAlert, although I imagine we'll wind up implementing various alert-handling policies as standalone widgets such as EAlertDialog. I'd like to try an EAlertInfoBar. Code that would otherwise display an error dialog itself would instead pass the EAlert to an appropriate EAlertSink and be done with it. Nothing is final yet. Still hacking on EAlert trying to find an API that feels right for these use cases.
* EAlert cleanups.Matthew Barnes2010-09-291-32/+10
| | | | Clean up the header, drop some unused cruft.
* Bug 628653 - e_alert_new_valist memory leakMatthew Barnes2010-09-031-2/+9
|
* Coding style and whitespace cleanup.Matthew Barnes2010-08-291-82/+82
|
* GObject boilerplate cleanup.Matthew Barnes2010-08-251-1/+4
| | | | | | | Prefer thread-safe G_DEFINE_TYPE and G_DEFINE_INTERFACE macros over manual GType registration. This is just a start... lots more to do.
* Coding style and whitespace cleanup.Matthew Barnes2010-06-201-8/+23
|
* Prevent future bugs like #612792.Matthew Barnes2010-03-151-5/+5
| | | | | | Add G_GNUC_NULL_TERMINATED to EAlert functions with variable-length parameter lists and drop the unnecessary "arg0" parameter so the function attribute works correctly.
* Add option to escape EAlert strings.Matthew Barnes2010-02-181-22/+34
| | | | | | EAlertDialog wants the primary and secondary strings escaped for use in markup text, EActivityProxy does not use markup. So make it an explicit part of the EAlert API.
* Bug 610085 - e_alert_get_primary_text() does not escape argumentsMatthew Barnes2010-02-161-17/+6
|
* Update API documentation.Matthew Barnes2010-02-101-0/+2
| | | | Also, start fixing some Gtk-Doc warnings. There's a lot.
* Coding style and whitespace cleanup.Matthew Barnes2010-01-311-2/+2
|
* Replace alloca() with g_alloca().Matthew Barnes2009-12-281-1/+1
|
* Coding style and whitespace cleanup.Matthew Barnes2009-12-201-4/+0
|
* Use gchar instead of char in e-alert.cJonathon Jongsma2009-12-091-1/+1
|
* Handle the case where error definitions don't include certain fieldsJonathon Jongsma2009-12-091-6/+19
| | | | | | Some error definitions don't specify a title or secondary text. Handle these situations properly. This was a regression caused by my refactoring. Fixes bug #604085.
* rename e_alert_get_buttons -> e_alert_peek_buttonsJonathon Jongsma2009-12-091-1/+1
| | | | | Make it obvious that this does not need to be freed like the other things that use get_* (e.g. e_alert_get_title)
* Refactor EAlert to make it a GObjectJonathon Jongsma2009-12-081-280/+249
| | | | | | This encapsulates things a bit better and will be useful in the future since it will probably need to be a GObject if we want to communicate EAlerts between the front- and back-ends
* Fix a bug in e_alert_newv() that was causing a crashJonathon Jongsma2009-12-011-6/+5
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=602963
* Rename EError to EAlert to match general use betterJonathon Jongsma2009-12-011-0/+698
The EError mechanism is used both for error dialogs as well as basic alerts or user prompts, so we should give it a more general name which matches this use. This patch also cleans up a few includes of e-alert.h (formerly e-error.h) that were not actually being used. https://bugzilla.gnome.org/show_bug.cgi?id=602963
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-18 03:27:03 +0800