Interface Bug with 2 monitors in LP8

I use 2 monitors tiled vertically to display a large track layout - in 7.2 I'd have to open the screenset and drag the window across to the 2nd screen - once I did this it would stay in place (across the 2 monitors)
I LP 8 I tried the same thing - only when I select a track on the 1st montor the display reverts and redraws the window to only ONE screen - so for now v. 8 is useless -
Also - I find the legibility is MUCH WORSE with this haze of grey over everything - Looks Like I'll be hanging on to my xs usb keys for a while---
back to work, back to 7.2

I work with 2 monitors all the time - with very large arrangements it's a huge boon. Are you saying if for example you have a linked matrix editor open on the 2nd screen every time you change tracks it shhots onto screen 1?
This would be a disaster for my use of Logic so I hope this isn't the case or if it is it's a soon to be fixed bug!
Julian

Similar Messages

Potential bug with dual monitors running Maverick

When running dual display monitors on a MacMini I have found and can repeat where 2nd display open windows need to be dragged over to the primary display monitor to activate then dragged back before you can actively select or do anything in that window no matter what app you're using. Apple mail is the worst.
Second - primary screen has to be thunderbold monitor to HDMI with the title bars at the top of the primary screen only.
Mirroring has to be turned off, the menu bars can not be on both displays otherwise you can not access the app without dragging it back and forth to activate it. With mirroring turned off - most programs run. BUT Apple mail still does not.
I am using two HDMI ASUS 24 inch monitors running Maverick 10.9 (13A603) on a MacMini: Processor 2.6 GHz Intel Core i7, Memory 16 GB 1600 MHz DDR3, Graphics Intel HD Graphics 4000 1024 MB.
any solutions? Bug or some setting I should change?

No, there is no way to set it up with two different interface (keyboard & mouse) setups.
Unfortunately, it sounds like your about to become a two or three computer family.

Launch Pad bug with Multi-Monitors in Mavericks...

I noticed something while trying to use a two monitor setup with Mavericks 10.9. After moving from the primary laptop monitor to the secondary monitor, I noticed that after clicking in the screen to make it the active screen that the LaunchPad gesture would not work. From there I proceeded to drag the pointer down to access the Dock. I noticed after touching the Dock in the secondary monitor, then LaunchPad gesture would work. If I try the LaunchPad gesture before touching the dock, the system brings up LaunchPad in the screen of the previously active monitor. I noticed the same senario when moving from the secondary monitor back to the primary monitor. So, in a nut shell:
1.) When moving from one active monitor screen to another, click in the inactive screen to make it the active screen.
2.) Move pointer to the Dock (wait for Dock to rise).
3.) After the first two steps, THEN the LaunchPad gesture can be used in the now active monitor.
Has anyone else noticed this? Now a big deal but it is an annoyance I cannot believe no one else has seen.

Thank you! Your solution worked for me.
It seems to be a bug in multimonitors.

Proofing bug with multiple monitors (InDesign & Acrobat on Mac)

Software:
InDesign CS3 5.0.3 and Acrobat Professional 8.1.2 (Mac OS X Leopard 10.5.4)
Both application does not compensate the onscreen colors when moving document windows to another screen.
I have three monitors: Eizo ColorEdge CG220, 30-inch Apple Cinema Display and 17-inch Apple Studio Display.
The 30-inch Apple Cinema Display is my default monitor (with the menubar). But the Eizo ColorEdge is my color-proofing screen. To get correct onscreen colors on the ColorEdge I have to set it as the default monitor in System Settings. That's a hassle. I hope this bug will be fixed.
Photoshop handles this perfectly.

AlFerrari,
My Mac Pro has two graphics card. The 30-inch uses the first one, and the Eizo and 17-inch shares the second card. The graphic cards are identical.
Gernot,
Photoshop refreshes the colors when releasing the mouse button after dragging a window from another screen. Acrobat and InDesign does not.

Lightroom 5.2 and Mavericks Lights out bug with dual monitors

I installed OS X Mavericks on my iMac which has a second NEC display connected and that I use as my main display. When I activate "lights out/lights dim" pressing "L" on the keyboard my primary display (NEC) doesn't change at all but the secondary display (iMac) is the one that dims the lights on the interface. Makes no difference if I have the secondary display active as a second screen for Lightroom or not. Lights out/dimm dosen't work on my main interface display.
Anyone seeing this as well with their second display?

I am having the same issue and wondered what was the issue. Thank you for posting; now I remember Lightroom didn't start doing this until I updated to Mac OS Maverick. The only time I don't have that problem is when I physically disconnect my secondary display from my computer.

BUG: Alt+Scroll to Zoom with 4K Monitor on Windows

Windows 8.1 users with 4K monitors and have Windows' upscaling enabled, please let me know if you can reproduce in the comments! If you have a Mac, you can try to reproduce too, to see if it's just a Windows thing.
I recently setup a 28" 4K monitor for my Windows machine, and upgraded to Windows 8.1, because it has better independent monitor scaling. I also still have a 1920x1080 monitor. (I don't recommend this setup and Windows 8.1 doesn't handle it well. But that's another story)
Premiere Pro is up to date: 2014.2 Release: v8.1, Caravan
By default, Windows has this slider set to the middle recommended setting:
This upscales almost everything seen in Windows, including Premiere Pro's interface.
There's one problem: While hovering over my Timeline, holding down the Alt key and scrolling my mouse wheel doesn't zoom in as it should. It zooms, but the location it zooms into is incorrect.
Here's how Alt+scrolling to zoom usually works:
- wherever your cursor is located is where you zoom in to. If your cursor is hovering over the CTI, you'll zoom in with the CTI centered. If your cursor is at the 2 minute mark, when you alt-scroll to zoom in, the 2 minute mark will be centered in the timeline.
With Windows 8 scaling turned on, the math that drives Alt+scrolling's centering algorithm is totally thrown off! It's hard to describe in words, so here's a graphic that shows exactly what happens when I place my cursor over the red spots and try alt+scrolling:
If the software was working as intended, the red & yellow arrows would overlap eachother, because your zooming should be centered right where the cursor is.
It's driving me crazy, as I rely on the Alt+Scroll method to zoom. Zoom Tool and the +/- keys aren't granular enough; and resizing the horizontal scrollbar is a newer addition to Premiere that I haven't needed to use just yet, as alt+scroll was working fine for me until upgrading to 4K.
Now, I did consider that my second 1080p monitor might have added to the math problems as it has a different amount of scaling applied to it, but I completely disabled the second monitor and ran tests and had the same bug, so the chance of my second monitor having any affect on this bug is incredibly slim.
Obviously there are workarounds:
Turn of the Windows DPI scaling. Fixes the problem instantly, but everything is really tiny on the screen, and isn't really recommended
Don't use the Alt+Scroll method to zoom.
I'm assuming this is only a Windows bug, but if someone wants to test this out on a Mac with a Retina display, that would be helpful!
Can anyone else reproduce this bug? If so, can we all file bug reports to make sure the message gets across? I've heard from Mark that that's the best way to make sure the Premiere team takes an issue seriously. If a bug is only reported by a single user, there's a chance that very few users are encountering the issue, and they won't prioritize a fix.

Hi Tim,
If it's not recommended to use the software when DPI scaling is enabled, it would be nice if the software would give you a one-time warning, letting you know that Premiere Pro hasn't been fully optimized to work properly when scaling is enabled.
Not a bad idea. Would you mind filing a bug report? http://adobe.ly/ReportBug
So, I just installed Premiere Pro the day of this post on a brand new machine. If Caravan isn't the current version, why is Creative Cloud still telling me I'm up to date? I've restarted my computer a few times... the the CC app should know what's apps are up to date and which aren't, correct? Or is it just a mistake that "Caravan" is shown in the about info?
This drives me a little crazy. I will bring this up with my colleagues. The actual version number is at the bottom of the "About Premiere Pro" screen. Because it says 8.1 at the top of the screen is confusing customers.
Another bug at higher DPIs that I noticed after posting this... plugins are cropped wrong. Here's what it looks like if I use a Dynamics effect:
It's annoying, but this one has an easy workaround... just resize the window to way bigger than it should need to be. Sure, the bypass button and presets are partially covered, but it's still usable.
It would be great to get a bug report about that, as well. Thanks!
So yeah, in conclusion:
It would be great if you could let your customers know up-front in the software that Premiere Pro isn't fully ready for Windows' hardware scaling. Photoshop has a HiDPI setting, but the dev team rightfully tucked it away in an experimental features section.
besides these bugs, the software seems to work as intended, so you guys are almost there, thankfully!
Thanks so much for reporting back.
Regards,
Kevin

Virtual Interface generation bug with NetWeaver ?

I use the Web Service generation wizard to generate a virtual interface which exposes methods in an EJB. As one of the parameters I pass a simple java bean, lets say:
public class StatusCode
    private String name;
    private boolean buggy;
    public String getName() {...}
    public void setName(String newName){...}
    public boolean isBuggy() {...}
    public void setBuggy(boolean trueOrFalse){...}
When I look at the virtual interface generated, especially at the Types tab, my boolean attribute is not included.
If I change the getter to "getBuggy()", the attribute is included in the VI. The only problem is that the typical Java Bean framework, say from sun or ibm, always map 'boolean' getters to 'isSomething()' and not 'getSomething()'.
Is this a bug with NW? Is there a fix or workaround for this ?
My version of NW:
Version: 2.0.7
Build id: 200407270250
Thanks in advance,
Mark
(If this is not the right forum, could someone suggest where I can post this question?)

Hi. As of Netweaver 2004s, the virtual interface piece has be absorbed into the creation of the web service definition, so there is no need to create it as well.   When you are getting the 403, how are you trying to run this, using the Web Service Homepage? If so, you will need to configure what j2e engine that you want to use to use. You can do this in WSADMIN under the Administration settings.   Check that this is set. YOu must know the URL of your j2e engine.
Regards,
Rich Heilman

Interfacing with dual-monitor machine

Hello all--
I've got a G5 at home with dual monitors on which I run 3D animation software with lots of panels. I'd like to be able to control the G5 from work using a laptop (possibly also connected to an external monitor). Is it possible to display both screens of the desktop using ARDv3 on the laptop? Some users have mentioned they can do this but the size of the remote screens is unsatisfactory. So, again, can you visualize both screens well via the remote computer?
Thanks for any help you can offer.

you can view both screens at once but it will be scaled to fit on the screen you have... so what you see is dependent on the resolution of both client monitors and your admin computer's monitor.
you can also select to view a single monitor of the client computer.
i've never run ARD admin on a computer with 2 monitors so i'm not sure how it handles it but i'm guessing that you can view both monitors on both admin monitors.... it'll probably scale down or up dependent on resolution.

Excel 2013 BeforeRightClick Event fails on Windows 8.1 Tablet (it's an Excel 2013 tablet touch screen interface bug)

I have developed customized table context menus in an Excel 2013 workbook on my Laptop. They work just fine on my laptop and my work desktop. But when I try to run them on my tablet PC the Worksheet_BeforeRightClick event in Excel 2013 never fires. Other
worksheet events appear to work okay. I have fully reinstalled Office 2013 Pro and that does not make any difference.
I have read other comments regarding this same problem going back to 2013, but have never seen Microsoft respond to this issue. Nor have I been able to find a resolution. Has anyone else run into this and found a solution?
Additional Discoveries: Testing on my tablet shows that adding one custom CommandBarButton to either the top or the bottom of the default "List Range Popup" context menu causes the Worksheet_BeforeRightClick event to fail. The basic context
menu commands still show up, but the default dropdown button for additional context menu commands disappears. The event is perhaps firing, but any customized code for the context menu is not being handled properly by Excel. This does appear to be a bug and
not a question of coding error. Perhaps someone else with a tablet PC running WIndows 8.1 could test this.
Based on comments
here this bug was introduced in Excel 2013 because others find the problem does not exist when using Excel 2010 on a tablet PC. Note that all the commenters on the linked thread that are experiencing this problem are using tablet PCs.
Update 3-13-15: I stand corrected. The Worksheet_BeforeRightClick does work on Excel 2013 Windows 8.1 tablets. I happen to own an Asus VivoTab Note 8, which comes with a Wacom stylus. If I use the Wacom sylus to right click on an Excel 2013 worksheet cell,
the Worksheet_BeforeRightClick event fires and modified context menu code runs just fine. But the code will not run if one uses their finger to right click a worksheet cell. This explains why this problem only shows up on tablet PCs. So the "bug"
introduced in Excel 2013 is a general user touch screen interface bug and not an Excel events programming bug.
Update 3-21-15: Switched to a Toshiba Protege laptop with touch screen. Same issue with finger touch screen interface on the Toshiba touch screen as with the Asus VivoTab touch screen.
Laptop: Toshiba Protege (with touch screen), Windows 8.1 64bit and MSOffice 2013 Pro 32bit
Tablet: Asus VivoTab Note 8, Windows 8.1 32bit and MSOffice 2013 Pro 32 bit
Desktop: Generic, Windows 7 64bit and MSOffice 2013 Pro 64bit
phillfri

Hello Phil,
Command bars were deprecated and shouldn't be used any longer. Instead, you need to use the Fluent UI (aka Ribbon UI) instead. You can read more about the new UI in the following series of articles in MSDN:
Customizing Context Menus in Office 2010
Customizing the 2007 Office Fluent Ribbon for Developers (Part 1 of 3)
Customizing the 2007 Office Fluent Ribbon for Developers (Part 2 of 3)
Customizing the 2007 Office Fluent Ribbon for Developers (Part 3 of 3)
As a workaround you can add a custom control to the context
menu with the getEnabled or getVisible callback which will be invoked before the context menu is shown.

Mac Mini Won't Boot with VGA Monitor Connected

I have a new Mac Mini connected to an older VGA monitor using the Apple brand VGA adapter. The mini is fully up to date and runs perfectly when booted. However, if I reboot the mini with the VGA monitor connected, it fails to boot. I just hear the faint chime sound every other second. There is no output to the monitor and the only way I can get it to boot is to disconnect the monitor and then power cycle the mini. I can reconnect the monitor just seconds after powering back on and it finishes booting properly.
Anyone else experience this? It is very frustrating. I've also tested with an HDMI connected monitor (without the VGA adapter) and it boots just fine and the display works properly.
Thanks!

Okay, I'm back with good news: I have found two remedies for the problem which will hopefully solve it for you as well.
Given that the issue only occurs when certain monitors are connected, I concluded that the root of it must be a bug in the Mac's firmware related to DDC (Display Data Channel) handling, and that the most promising way to address it should be to just disable the DDC.
Workaround #1: If your monitor has BNC connectors, use a VGA to BNC cable.
In this configuration the DDC pins are not connected to the monitor at all. This did indeed fix the problem - my Mac mini booted without a problem with the monitor connected. However, I was not completely satisfied with this solution, because VGA to BNC cables are usually quite heavy and inflexible, and do no go together well with Apple's MDP to VGA adapter and the Mini Displayport/Thunderbolt port which has no locking mechanism.
Workaround #2: Remove pin 12 of the VGA plug.
Pin 12 of the VGA plug connects the serial data line of the DDC. Pulling out this pin with a pair of needle nose pliers will effectively disable DDC. I hesitated to do this to my cable (a direct MDP to VGA cable which eliminates the need for a separate adapter dangling from the Mac) and therefore bought a tiny VGA male to female adapter (also called port saver, e.g. Delock 65250) to perform the surgery on that. This has done the trick and my Mac mini has started up fine ever since.
Of course, without DDC the Mac won't know the model name and capabilities of the attached monitor and thus offer some resolution and frequency settings which the monitor may not support, but that's a small drawback compared to having to pull out the monitor cable everytime you turn on or restart your Mac.

Help required to set monitor screen in Ultra 10 with IDE monitor

Hi
I bought a Ultra 10 Workstation machine, I have both monitor interface
1 regular IDE monitor interface
2 Default Sun monitor interface.
But i dont have default sun monitor, that is why, I took out AGP interface, and I hooked up regular IDE monitor interface. it shows display, but all the fonts are very big and even the CDE GUI interface, is also with big fonts....
I need to know, how to fix this problem..
Please help me,
I will really appreciate your help.
Thanks

Both of you are posting in the wrong forum. Additionally you complain about Sun taking to long to repond....maybe if they weren't being bothered by questions like this they'd respond faster. Searching on google for one minute would have turned up results, better yet going to http://docs.sun.com and searching for "change resolution" shows the information that you need as the FIRST result.
But to answer your question so you don't have to search....on Sparc system the video card and monitor are suppossed to figure this out during setup. Some video card and monitor combos can't. This usually means the monitor and the video card don't support the same resolutions and refresh rates or the DDC info couldn't be obtained from your monitor.
On Sparc Solaris you need to run a command specific to your video card. The most common one is for all ATI based video cards, "m64config".
Under x86 Solaris(not Ultra10s but just to be complete) you'd run kdmconfig from the console.

[Non IE Regression] Support for full screen mode with multiple monitors

This seems to be a regression with Flash Player v11.2.202.x (for all other browsers).
With Internet Explorer it is still working.
http://kb2.adobe.com/cps/890/cpsid_89050.html
== Support for full screen mode with multiple monitors ==
Full screen content will remain in full-screen on secondary monitors, allowing users to watch full-screen content while working on another display.
Tested on Windows 7 x64 SP1 with:
- Internet Explorer 9
- Firefox Release, Beta, Aurora, Nightly
- Opera 12 build 1116
In bugbase.adobe.com I cannot choose v11.2.x

Please vote for it If you have the same problem:
https://bugbase.adobe.com/index.cfm?event=bug&id=3016912
Thanks

User Interface bug when renaming tracks in list views

When renaming tracks in the list views, there is a user interface bug that makes it impossible to see what you're doing. When you select a track in the list view, this is what it looks like:
Note how the text is white on the darker blue background. When you click again, to open the inline text editor to rename, this is what you get:
The background color of the text editor is white, just like the text, so when you type, you can't see what you're typing, nor can you see where in the original text your text insertion cursor is located.
Thanks!
Steve.

I'm frustrated with this same problem. In my case this happens only in my 10.5 macbook air and not in my 10.4 macbook pro. I've been renaming files in the same way in 10.2/10.3 and this never happened. Should be a bug. I've been searching for this issue and found this post at last - I really wonder why there aren't so many people mentioning this.

[SOLVED] Modesetting with external monitor broken (intel)

After recent updates, modesetting during boot no longer works if an external (vga) monitor is plugged in.
Once it gets to modesetting, both screens go black and I can't tell what happens after that (Might hang, might boot fine I just can't see it…) The external vga screen is black (with very occasional horizontal line of noise), but remains on (It doesn't go to sleep, which it usually does if not receiving a signal).
If the monitor is unplugged during boot then plugged in once the login prompt is reached, modesetting works and running X multihead with xrandr seems to work normally. (workaround until the issue is solved)
Changing from Early KMS start to Late KMS start means the black screen appears later, but it still appears.
Booting with nomodeset works with the monitor plugged in, but means X fails to start with an error message about not finding any screens.
The laptop is an old macbook, with integrated intel graphics card:
Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
Last edited by Thrall (2013-03-19 11:29:04)

Ok, I'm trying to collect information for a bug report, so if people could confirm or correct what I have so far and add any additional relevant information, that'd be very helpful.
The fact that running the linux-lts kernel fixes the issue suggests that the problem almost certainly lies with the kernel.
Comparing the date of my first post with /var/log/pacman.log, I believe the upgrade that first caused the issue to appear was this:
upgraded linux (3.7.3-1 -> 3.7.4-1)
(There is a very slim possibility that I managed to upgrade to 3.7.4 without actually rebooting into the previous kernel, in which case the issue could have been present in an earlier version, but I wouldn't have encountered it.)
So far, the only graphics card affected appears to integrated intel chips:
Intel Corporation Mobile 945GM/GMS(/GME), 943/940GML Express Integrated Graphics Controller (rev 03)
Has anyone observed this issue with a different graphics card? (check the output from entering "lspci" in a terminal if you're not sure how to find out)
Finally, Wittfella found reinstalling from scratch fixed the issue. If someone can come up with a reasonable explanation as to *why* this fixed it (and ideally narrow it down to changes that can be made without reinstalling from scratch if at all possible), then it's possible that it's not an actual bug, so much as a poorly documented change that causes problems upgrading but is otherwise ok afterwards.

Firefox not remembering window size with two monitors

I have a laptop with a monitor attached - both the laptop monitor and external monitor are used as separate desktops. I have Firefox set to open on the external monitor, but it does not remember the last window size: it always opens to the size of the laptop monitor. Firefox is the only program that exhibits this behavior. I have reset, uninstalled and re-installed, yet the same behavior continues. Before re-installing, I've made sure to delete any left over Mozilla/Firefox folders.

As far as I can tell this problem was never fixed and it goes back years:
[https://bugzilla.mozilla.org/show_bug.cgi?id=251024 Bug 251024 - On startup the main window is incorrectly sized according to the workspace of the primary monitor]
Even more bugs about it here:
https://www.google.com/#q=firefox+dual+monitor+size+site:bugzilla.mozilla.org

Interface Bug with 2 monitors in LP8

Similar Messages

Maybe you are looking for