![]() If its true this is a bug from Apple, I really hope Apple will fix it soon - Mavericks has been out for quite a while now.įor inkscape in particular, I have a work-around.similar tricks should work for other X11 software like GIMP: I can open the Inkscape menus via keyboard commands, and they sometimes appear in a corner of the screen, so I managed to try Inkscapes own "full screen" option, but also this one did not help. It seems that X11 mixes up the size / positions of the two monitors, or sometimes adds them together in some way. Zooming the window (via menu) sometimes (depending on monitor positions) results in the window being completely below the lower monitor, or sometimes getting the size of the larger monitor. Moving it into other space does not change the window location. Inkscape does lanch, but I only see the bottom right corner of the Inkscape window, and there seems to be no way of getting the title bar into the visible screen area of any screen. I have a related problem, pity that zabbarob's workaround does not work in my case:ĭual monitor setup (secondary screen above the MacBook Pro screen), MacBook Pro late 2008, Mavericks, Inkscape binary 0.48.2, XQartz 2.7.5.Mission control setting "Separate Screens for Spaces" enabled. * invisible windows to the right of the visual area become visible doing this trick on the right monitor * invisible windows to the left of the visual area become visible doing this trick on the left monitor it depends on where invisible windows are located: ![]() If it doesn’t work with creating a desktop on one monitor, try it with creating a desktop on another monitor. * ⇒ invisible windows get repositioned and are shown * ⇒ app windows from that desktop are moved to another desktop * create a new desktop in Mission Control so i can't see or select and therefore can't move the document properties window. once i select file > document properties they open on the left "hidden" part of X11's "window". That hack didn't work for me, but I figured out another way to move windows into the visible area.īackground: i have a MacBook Pro, with my external monitor to the left of my laptop i open inkscape on my laptop monitor by typing the app's name into spotlight on the laptop's monitor. (the reply doesn't seem to be available in the ML archives yet) > be a satisfactory stop-gap until the issue is fixed in a future > Hopefully the "disable Displays have separate spaces" workaround will > for the OS-side of the solution in a future OS update. > to address the bug with an XQuartz update, and you'll have to wait Unfortunately, this means that I won't be able > the fix requires changes to both XQuartz (specifically libXplugin) > This incompatibility with multi-monitor support is a known issue, and ![]() > you will loose out on all the useful updates to multi-monitor > XQuartz will behave nicer with multiple monitors in that mode, but > Yes, disabling that checkbox returns you to a "legacy mode" of sorts. ![]() > windows to span displays, instead of fading out on one. > "Displays have separate spaces." Doing so also allows application I unchecked all boxes, but the relevant one is > The controls I used were in the System Preference pane for > spans the two displays, as the system has since 10.6. > piece of pixel real estate), was able to run an animation that > as they have since OS 6 or so (that is, one large, contiguous > unlikely location of the controls for freeing the displays to act > after finding (in what's becoming an Apple tradition) the I installed Mavericks on a two-monitor system today, and On 10:40 +0200, Jeremy Huddleston Sequoia wrote: ![]() Possibly related: a XQuartz issue with multi-monitor setup on Mavericks just discussed on the X11-user mailing list Do you have any other GTK+ applications installed which use the X11-backend of GTK+? Note that current official GIMP packages do no longer use X11 - they are all built with the Quartz backend of GTK2. These items will not work tested version 3.48-3.> Gimp, which also uses x11, does not have this problem. Or use a GUI interface: LaunchControl Not Working Move to the father folder where you want to install Domoticz and run: Use the Terminal and execute the commands below note that Z-Wave is not included you have to compile that yourself:Ĭontinue at section: Make Domoticz startup at boot time (Also needed for Web Update)Ĭontinue at section: Make Domoticz startup at boot time Preparing your OS X for Domoticz Get Xcode command line toolsĬompiling requires Xcode, which can be installed with command line:Įxport LDFLAGS =-L/usr/local/opt/openssl/libĮxport CPPFLAGS =-I/usr/local/opt/openssl/include 1.6.3 Download Domoticz and OpenZwave source.1.6 Compiling Domoticz with OpenZWave support for MacOS Sierra (10.12). ![]()
0 Comments
Leave a Reply. |