On 02/09/17 18:23, Norbert de Jonge wrote: >> I save preferences per monitor > > I think giving us more context might be useful. What kind of things do > you save per monitor, and why? These are not things you could recreate > by scaling and positioning based on detected monitor dimensions?
The saved settings are mostly for aesthetics. Monitor background, slideshow preferences. So the monitor geometry does not affect what I do. > If we're assuming monitors can be arbitrarily plugged in and out, and > detection is unreliable or users may even have unidentifiable monitors, > no function will ever help you. If this is not a cross-platform > application and you _really_ need to recognize monitors, your program > could make a system call to "xrandr --prop" and compare EDID strings. The application already works with gtk2 where it uses gdk_screen_get_monitor_plug_name and the index in gdk_screen_get_n_monitors. It works ok but I was hoping to get rid of the last corner cases with the new API. However, if there is no straightforward way to achieve this, then this is a limitation I have to live with. Are there any statistics how many monitors do not have a model returned by gdk? > If you have a broad range of users, all GTK+ 3.22 and newer functions, > including both gdk_monitor_get_model() and gdk_display_get_monitor(), > may be problematic. > 3.22 is the target. There is an old version of the application running with gtk2 that those distributions can ship. _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
