This IS the Avid L2: Re: [Avid-L2] [BUGS] ??? in v 7.0.2

Dave,

Thanks for that insight on the monitor behavior. I will give that a shot.

And you made me laugh with your comment about "Geezer Mode."

I thank you for that as well.

I lower the monitor resolution too, when I'm doing color correction.

And if it makes anyone feel any better, even the whipper-snappers I teach,

with much better eyes than mine,

love when I show them how to zoom in on a Mac:

System Prefs > Universal Access > Zoom > Options >

Use Scroll Wheel with Modifier Key to Zoom.

I can't live without it!

Thanks again!

Cheers,

Benjamin

----

Benjamin Hershleder

Book: http://tinyurl.com/AvidMC-Book

Film: http://TheBronxBoysStillPlayingAt80.com

Site: http://ContactBen.com

On Oct 24, 2013, at 3:54 PM, Dave Hogan wrote:

As to bug number two, I do a similar setup with workspaces, and my Effect Edit workspace has a single monitor.

I too was experiencing the phenomenon of it switching back to dual monitor when I switched away and back, though I found a workaround of sorts...

When setting the max size of the Single monitor window, it does a slight hitch, going wider at its full size. I have found that if I set the size just below where it does that hitch, that the display reliably stays single monitor when switching back and forth to my effects edit workspace.

I am on a Mac Pro tower, running MC v7.02, Lion and Unity.

Another note is that I find that on some very high res monitors even the full size single monitor is not large enough for detail work in paint, tracking or animatte. So I just reduce the overall resolution of the monitors, thereby making that maximum size bigger. You go far enough, (768 height) you can almost fill the screen with a single monitor...something I like to call "geezer mode."

Dave Hogan
Burbank, CA

On Thursday, October 17, 2013 12:23 PM, Benjamin Hershleder <Ben@ContactBen.com> wrote:

Thanks Terry.
I guess that bug goes hand in hand with the
"fly up to the top left corner of the monitor" feature ;)

Cheers,

B

On Oct 17, 2013, at 11:56 AM, <tcurren@aol.com> <tcurren@aol.com> wrote:

Bug number 2 has been there since 7.

__