Hello, Was hoping that someone could add this so no one else does something as stupid as I did :) Was playing about with the resolution change part of the Display Preferences option in the settings manager when set it to a very low resolution. When you do this it changes it but you can't get it to change back without being able to see the panel, which you can't see because it's outside the viewport of the desktop. Anyway, I was wondering would it be possible to have a dialog box that says "Are you happy with this new resolution" or something similar, which would, after a set time of maybe 30 seconds if no confirmation was received, reset it to the original resolution. Reproducible: Always Steps to Reproduce: 1. Change resolution to something ridiculously small 2. Realise you can't see the viewport 3. Alt-tab about until you focus the Display preferences applet. 4. Get frustrated. 5. Kill X. 6. File request. 7. Learn lesson not to mess with the resolution for no reason other than you're bored. Actual Results: I felt stupid and filed this request for a new feature. :) Expected Results: It'd be nice to have a timed dialog requesting confirmation from the user that they're happy with the new resolution and if no response or they're not then it resets to original res.
I think this is pretty worthwhile. Most windowing systems have a timed confirmation when you switch resolutions as a safety against getting into an unviewable state.
Created attachment 373 Patch to add timed confimation of resolution change Would this make it? It would also be nice if the display settings dialog would be kept on the center of the screen after the resolution change. This could be done with xfce_gtk_window_center_on_monitor_with_pointer(), but it does not seem to work unless pending gtk events are processed before calling the function. I seem to recall that careless calling of gtk_main_iteration() might result in deadlocks in some cases, so I didn't include it in the patch.
This never made it to Xfce, did it? Item for 4.6?
It made to 4.4. It was merged as part of another bug, whose Bugzilla item I don't seem to be able to find.
Fixed in git master.