Closing a plugin window shouldn't select the associated project

Author
Post
Essentials Only Full Version
mesayre
Max Output Level: -87 dBFS
  • Total Posts : 195
  • Joined: 2012/07/07 09:29:57
  • Location: New York, NY
  • Status: offline
2015/06/11 13:29:40 (permalink)
4 (2)

Closing a plugin window shouldn't select the associated project

Hey all,
   This is a little one, but I find myself annoyed by it on the regular.
 
   When I work with multiple projects open, I switch between them using the window menu, or CTRL-Tab. But when i switch to project B, if I had a plugin window from project A open, it stays there open over Project B (to which it does not belong). Now there are some reasons people might want that behavior, but when I then attempt to close the window and get it out of the way, it then puts the focus back on project A. So unless I remember to close the windows of all plugins before switching, I have to switch twice!
 
Seems like either A) Plugin windows should minimize when their project loses focus, or B) at least there should be a special exception that lets you close a window without switching focus to its project.
 
Thanks for considering,
Mike
Win7x64 Sonar Plat Everest
#1

1 Reply Related Threads
    KPerry
    Max Output Level: -44 dBFS
    • Total Posts : 3120
    • Joined: 2011/04/26 15:13:15
    • Location: London, UK
    • Status: offline
    Re: Closing a plugin window shouldn't select the associated project 2015/06/12 02:37:57 (permalink)
    0
    B would be better - it's sometime helpful to be able to view settings of the same plug-in in different projects to check settings (for those 'why is this behaving weirdly?' moments!).
    #2
    Jump to:
    © 2024 APG vNext Commercial Version 5.1