Re: Desktop as transient window


i think this is a case when the warning, (which can be ignored), is meant for the developer, and not the end-user.

i would trap the error, ignore it, and definitely not forward to the end-user; following the dictum "avoid confusing them as much as possible..."


On Mon, Aug 10, 2015 at 12:12 PM, Igor Korot <ikorot01 gmail com> wrote:

On Mon, Aug 10, 2015 at 1:01 PM, Paul Davis <paul linuxaudiosystems com> wrote:
> On Mon, Aug 10, 2015 at 12:57 PM, Jasper St. Pierre
> <jstpierre mecheye net> wrote:
>> Hi Paul,
>> In recent GTK+ versions, GtkDialog emits a warning when it is mapped
>> without a parent, saying that it is discouraged. See

The trouble is - it is a legitimate use case when the dialog has no parent
or the parent of the dialog is a Desktop/WM.
It means that this dialog has system modality vs. application modality.

In addition I just gave one legitimate use-case where the application
is dialog-based
and the main frame comes in later after the dialog is gone.

Most users will just ignore it but some will file a bug report saying that this
is a bug in the software, whereas this is an issue in the underlying toolkit.

Thank you.

> I should my mouth/fingers closed/still when GTK3 is on the table.
> Sorry for the noise. This warning seems unfortunate though. GtkDialog
> is a useful class and doesn't inherently need a parent. Does it?
> Using transient-parent on OS X is a very bad idea, and it really buys
> nothing with tiled WM's either. It is very regrettable that X (and its
> successors) have not implemented a more sophisticated app-centric
> window layering model.
gtk-list mailing list
gtk-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]