On 11/07/2011 07:40 AM, Thomas Martitz wrote:
Am 07.11.2011 16:34, schrieb Colomban Wendling:
However, I'm not sure fallback to modal dialog is that good… let me
explain: a GtkInfoBar is a kind of non-intrusive messaging to the user,
where modal dialogs (or dialogs in general) is intrusive. This means
one could easily "ignore" the info bar but not the dialog.
I assumed the editor widget would be frozen/set read-only until the info
bar is processed by the user, so both seem intrusive.
It doesn't currently do this, but it would be trivial. Out of
curiosity, why is this important? The way I see it, if a file was
changed on disk, the user wants to do one of three things:
1) Reload the file from disk, over-writing their changes in the buffer.
2) Ignore the changes on disk and continue editing the file, possibly
saving with a new filename later.
3) Close the document? (which can be done by clicking the tab close
button which is just above where the infobar pops up).
Maybe there is some use-case I'm not seeing?
OTOH the info bar would probably allow switching documents without doing
anything which would solve a (for me) major annoyance with the modal
dialog when ctrl-tabbing through docs. So not equally intrusive.
This was my #1 inspiration for writing this.
What solution can you suggest? I find the info bar superior and don't
care about the fallback really.
The fallback is only to support GTK+ v2.16, since it doesn't have
GtkInfoBar yet.
Cheers,
Matthew Brush
_______________________________________________
Geany-devel mailing list
Geany-devel@uvena.de
https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
