[Work Around For Now] PRV Not Remembering To Remain Full Screen

I don't seem to be able to resolve this issue now either...
 
I used to run PRV in it's original (pre-Multidock) mode as a full screen item which would remain as a default... There was an acronym for this mode which I recall finding it under the icon in the left upper corner (where maximize and such is also located)
Screenset is not locked
I have removed the PRV from Multidock and maximized it yet everytime I open it, I'm back to floating small window...
 
What am I forgetting?
 
Thanks!

I and others have had the same problem with the PRV in the past. Here's my fix: works every time. Another fellow I PM'd said he used a similar fix.
1. Open new project.
2. "Shift+D" the mixer/console. (I use a single monitor, so I'm not sure what happens here with a multi-monitor setup.)
3. Close the mixer (close the tab in the multi-dock, don't just use the hotkey).
4. Open the mixer (Alt +2), or pick from the View menu.
- 4a. At this point the mixer should should be opening to it's max height.
5. Open a PRV, it should now open to max height as well.
 
I'll be watching this thread to see what the "real" solution is, because, dang it, that's just not the desired behavior.

Thanks Gang...

System is down for the evening, but I will try these ideas tomorrow morning...

Thanks declan... I'm very fortunate to have been gifted so much from my wonderful, generous friends!
Thanks zrapture... I thought Ctrl-D wa to zoom the multidock?
Thanks chuckebaby... I was thinking of trying that, but second thought told me a locked screenset would frustrate me in other ways?

zrapture
Hmmm, I happen to have a fresh installation here in front of me. By default, Ctrl-D is not assigned to any action. Maybe you're using a ProTools/Logic/Cubase/Nuendo/other custom set of shortcut keys?
 
chuckebaby, I'll have to read up some more on screenset locking. Do you happen to know where the default screenset files are stored, so that I can get back to them if I really cheese something up? Or maybe that's what Revert Current Screenset does.

they made it idiot proof for us bro. just click the drop down menu where screenset are and select "Revert screenset"
it sets the edited screenset back to its default.
 
let me tell people something. I used to look at screensets as one of those wasted upgrades that I would never use.
a toy if you will.
when I kept opening projects, spending 20 minutes changing all my lay outs so I could open PRV, console view, Track view. I said, why chucky...why ?
 
So one day I spent 20 minutes creating it once.
now every time I open a project, I import my screensets in to the new project (wish there was a way to store them)
now if I want PRV full view, I click #3
if I want track view only, I click 5
if I want a huge track view (what I call automation view) I click #7.
if I want Matrix...never mind I don't like Matrix
 
anyway, you guys get the point. rather then opening closing windows all day, I just click numbers to change the views.
 
its the best idea since  sliced bread threaded bolts.

Bristol_Jonesey
That's EXACTLY what Revert Screenset Does - reverts it to it's saved version, no matter what you do to it.
 
Changes to a current screenset will only be made permanent if you save the project AND the screenset is unlocked.

I said it first.
 
but you posted it before me.
 (the timestamp)

Every post I make says it was posted 30 minutes ago!

1.Undock the Multidock.
2.Maximize it.
3.Now press D it gets minimized.
4.Press D again to get it back
Just the way you kept it fully maximized. You wont get the floating window. If you use mouse click to minimize this wont work. Remember Undock the multidock, not the PRV. Open PRV in the multidock and click the undock button of multidock. You can also have the console view or anyother view this way and toggle by pressing D.

sonarman1
Update: If you minimize with mouse click it still works but you have to press D twice.

Hmmm, I happen to have a fresh installation here in front of me. By default, Ctrl-D is not assigned to any action. Maybe you're using a ProTools/Logic/Cubase/Nuendo/other custom set of shortcut keys?

Ctrl-D does nothing. I guess he meant Shift D. Which is used to toggle maximize in the docked multidock. 

CTRL + D makes me feel good inside though.
as long as im pressing a button, I feel like I have accomplished something.
so by pressing CTRL + D, though it has no effect. I feel like I have something.
that little extra something to make my mix sound just that much better.

Bristol_Jonesey
20% - 40% better?

your shooting to low BJ.
im talking like 75-80%

sonarman1
1.Undock the Multidock.
2.Maximize it.
3.Now press D it gets minimized.
4.Press D again to get it back
Just the way you kept it fully maximized. You wont get the floating window. If you use mouse click to minimize this wont work. Remember Undock the multidock, not the PRV. Open PRV in the multidock and click the undock button of multidock. You can also have the console view or anyother view this way and toggle by pressing D.

Thanks sonarman... I'll give this a try...
 
 

 You dont have to close it at all. I always keep it minimized. After double clicking on the desired midi clip just press D.

I will look at the concept and see how/f it works for me. I always feel uncomfortable with things left hanging around my main screen... I continuously and somewhat randomly switch between main widow needs and various midi clips/tracks...

So far, the work model where I simply dbl-click on a desired clip/location and replace the main screen with the PRV (back and forth) has been a very intuitive and comfortable wa for me to work... I have done this ver since Cakewalk made the change from sequencer to DAW... I don't relish changing that after so many decades, but of course I will if I have to (?)...

Does anyone know if MDI mode has been lost due to OS changes (moved from win7 to win8.1 is where this got lost) or Sonar changes? Or maybe it's still here but available through some other method than previous?

For now I've got my main screenset so that dbl-clicking on a midi clip opens a large floating PRV window and that will have to do... For now...

This is very sad if it is the case. I am progressively having more issues with Sonar related display issues... My long posted discomfort with Lane zoom min/max and this new issue continue to plague my every day of work. If we never had these things I wouldn't know how much better things could be (for me) and simply dream of having... But after already having and now losing these comforts... It feels "bad"

Thanks for all your kind and helpful ideas!

Keni

Keni,
  Multi Document Interface (MDI) mode works fine for me in Win 7 x64, so if you can't get MDI to work it must be the OS change that is preventing it.
I used the instructions posted by @Brundlefly here:  http://forum.cakewalk.com/FindPost/3443287.
 
Below is an example of Sonar 2016.06 in MDI mod.
 

 
Hope this helps,
-- Ron

rogeriodec
I solved this with Autohotkey: http://forum.cakewalk.com/FindPost/3398942

Thanks rogeriodec...

I've often wished for a macro recorder built into Sonar... I will look into this regardless of its application here.

I looked at your post but the script you created is only partially visible. Can I get a full copy?

Keni

rogeriodec
I solved this with Autohotkey: http://forum.cakewalk.com/FindPost/3398942

Thanks rogeriodec...

I've often wished for a macro recorder built into Sonar... I will look into this regardless of its application here.

I looked at your post but the script you created is only partially visible. Can I get a full copy?

For me the script is appearing completely visible (at least using the Chrome browser). Anyway, here's the complete script (without the "code" tags to avoid formatting in this post):
-----------------------

SetTitleMatchMode RegEx
#IfWinActive, ahk_exe i)SONAR.*exe
~LButton::
If (A_TimeSincePriorHotkey<400) and (A_TimeSincePriorHotkey<>-1)
Gosub maxprv
Return
~!3::
maxprv:
sleep 200
WinGetTitle, Title, A
IfInString Title, Piano Roll
Send #{Up}
Return
#IfWinActive
 
 
-----------------------
 
If you have any difficulty to install and run a first script, just follow the first steps in this tutorial:
https://autohotkey.com/docs/Tutorial.htm