SCREEN_CONTROL_LAST_SETTING usage

I am trying to figure out how to use the following items from the preferences file. No matter how I manipulate them, the graphics preview window loads the same way:

Perhaps I am missing something?

What I am trying to accomplish is having the zoom level be "zoom all" and display the entirety of the machine's extents when the GUI starts, or when no programs are loaded, etc. Any ideas otherwise?

Yea, it seemed like it wouldnt be easy.  No worries, it's not a huge deal, just was a rabbit hole I had started down.

What is the correct use for the [SCREEN_CONTROL_LAST_SETTING] stuff in the preferences file?  I cant seem to get them to affect any change in the GUI...?

Thanks Chris, I’ll take a peep then

I've worked out the user button stuff, thanks for the nudge in the right direction.  I am not using ActionToolButton though, in favor of two separate buttons, one to set the view stuff, and one to change to that view.  Calling ACTION.SET_GRAPHICS_VIEW('record-view') and ACTION.SET_GRAPHICS_VIEW('set-recorded-view') respectively.

What I haven't worked out is how to have the user view be the default view on GUI load.  It seems if you try to call the set-recorded-view before the graphics window is shown, it causes the works to crash.

Is there a way to do this?  Since there are pyqtProperties, I thought maybe there was a way to do it with stylesheets, but nothing I tried worked.  Hopefully I missed something simple?
 

I had pieced together that might be how it works (the clue for me was tracking the z or p value), thanks for the insight!  It seems to work well, I noticed your note in the docs about setting and then immediately trying the view because sometimes it doesn't take.  I also noticed that about 1 in 30 tries it doesn't apply the view correctly for some unknown reason, maybe the zoom thing you mentioned.

At any rate, even if it is "hacky", I do find it super useful as well.  I like zooming to the extents when there is no program loaded.  I always find I zoom too fast and too far on the table, and having a button to click is pretty nice.

For testing and what not, I currently have it set so that upon completion of homing, it sets the view to the user view (if the user has chosen to make it the default view via preferences).  It seems to work well, but maybe there's a better way.

I don't know exactly how it works, but when you load a program, it automagically zooms to what seems like the extents of the boundary for the program.  I then wonder how difficult it would be to add an option to zoom to the extents of a bounding box created by the X and Y limits instead.  

Killing a little time waiting on Christmas Eve festivities to commence over here on the east coast of the US.  So Merry Christmas to anyone reading this!

Figured I'd take a minute and give an update... Adding the user view is officially in the pipeline, I definitely see value in it, and I think others will as well. Phill had a good idea for double clicking the button to change it to SET, so I incorporated that and it seems to work well. Also, I made it so upon clicking SET, it records the view, and then immediately applies it so the user can tell right away if it stuck or not.

A few comments from things I learned/saw during the process:

1. I wonder if anything can be done to make applying the view more stable? I am willing to do what I can to help here, if you can give me some nudges in the right direction as far as where to look, and how it's working/what the current programmatic issues are?

2. If you had the grid showing, and if you are in a P view, and change to the User View, the grid will not be displayed. However, I noticed that if you go to Z view first, then click User view, the grid will be shown. The current work around I've implemented is to switch to Z, then switch to User View, it seems to be unnoticeable, but wanted to report back on it in case it can be fixed at the source.

3. Along the lines with #2, but not having to do with User View, if you have a grid applied, when you click P, the grid will disappear. I've tried Axis, and this mimics axis functionality, but the thing that makes me question if it is correct is that if I do the following, the grid will be shown in a P view:

a. click P
b. set the user view to that view
c. apply the user view (which in QtPlasmaC's case, sets Z first, then applies the user view)
d. the grid will be shown in a P view

Anyhow, again, willing to help however I can, but some of this is probably over my head.

Thanks, and I hope everyone enjoys the holidays!