CarpeThis

Has anyone esle experienced this? I am running Vista and have WindowBlinds installed but turned off (Using Aero) Acrobat reader 8.0 open fine, but when I right click on the OD zoomer icon Acrobat Reader crashes (Windows Dialog Application Stopped Responding). OD seems to still function correctly. I know it seems like an Acrobat Reader issue, but if I turn off OD and use the Windows task bar, the right click context menu (Close, Minimize, Restore,etc...) works just fine. <

I've also posted to the thread you linked to... I'll just follow that thread.... Thanks!

Thanks for the quick reply. Oops, I'm sorry about not including the specifics... Ok, I've installed the latest OD beta 1.58a[b].009 This is on Windows XP SP2 (all current updates) Very clean system (nothing else funky running except Avast Antivirus) Yes I am using WindowBlinds 5.5.023 (I haven't seen any of issues where it's staying on top of or under just

I have been testing the beta and the "Always On Top" feature. It is much better at staying on top for normal applications, which seems to solve the problems I was having in the previous versions. However, there are a few full screen apps where the docks continue to stay on top when they should be hidden/bottom. The apps I've tested are, Internet Explorer(i.e. F11 for Full Screen) Faststone Image Viewer 3.0 and Firehand Ember. In the previous OD version, it acted correctly and the doc

The update to v1.00.001 reset all my settings back to the defaults. Great program but it gets old having to reset everything after eash update... I was Hoping this would be fixed in the 1.x release.

I've been waiting for OD to support putting the docks in the desktop reserved area for awhile now, so I was happy to see it in the latest build! I use a reduced desktop area ( I have a reserved space on all sides of the desktop ) to display shortcuts, stats, meters, etc... When I select to have one of the tabbed docks reserve the edge of screen, it does reserve the correct side

Same issue here... I can't recreate it at will, but I notice it frequently when I'm working in Visual Studio 2003/2005. Seems like running apps in Debug mode frequently triggers the problem. Great update by the way....