I am using the undocument CGSSetWindowWarp function. Unfortunatly, in Lion, it stopped working properly (it works but all mouse events are dropped)
Is someone else encountering teh same issue and have a workaround?
Thanks and regards
From what I understand, CGSSetWindowWarp is primarily used by the Dock to transform windows which are in the process of being minimized. From this standpoint, disabling mouse events is kind of a feature (since it prevents you from accidentally clicking controls in a rapidly transforming window) -- it's unlikely to be fixed.
Related
I have 144 Hz monitor, when I move mouse around Unity Editor interface the it feels like the Unity drops refresh rate to 30 Hz (The mouse movment is very laggy, compared to other software's interfaces). Any suggestions how to solve it? THX!
While the accepted answer certainly does work, if you rather use a targeted approach you can also change the monitor refresh technology for Unity.exe to fixed in the control panel. This will address it for Unity and not force GSYNC in full screen only for other apps. You have to restart Unity for it to take affect.
Screenshot
after digging around I found that GSYNC was the issue. After switching to ONLY FULL SCREEN mode it worked!
Do you have some editor processes running in the background? Perhaps from a 3rd party tool? Sounds like it is checking for something expensive.
Go to Window/Analysis/Editor Iteration Profiler to test what could be slowing down the editor.
Another thing that comes to mind, are you using a laptop with a discrete GPU? You could have a power saving feature enabled to run graphically intensive applications (such as the Unity Editor) at a lower frame rate.
Unity won't let me select objects on my scene without first selecting the object in the Hierarchy. This was all I could find on the issue.
However, it seems that they decided that closing and opening the scene window fixed the bug, but not so with me. Also note that I am on a blank project. Its been really difficult to work around this bug.
Edit:
I have even uninstalled Unity and reinstalled with the hopes that this would solve the problem, but unfortunately it did not. Thanks for any help ahead of time.
Honestly this is such an odd problem that I'm having difficulty knowing how to try and fix the problem. I also reported the bug as recommended below by NoëlWidmer, but even the staff who was very kind had no idea how to deal with the problem, and the advice he gave also didn't change a thing. Truly, I don't even know what more information I can give you guys because as I said I literally opened a new Unity project for the first time after reinstalling and was unable to select without first clicking on the hierarchy. Is this just a special freak case that landed with me or has this happened to anyone else?? Also I'm using a two year old Windows 8 Laptop with literally nothing installed on it but the Adobe suite and a few other game developer necessities, so my computer most likely is not the source of the problem.
Edit: a Clue??
Well I was messing around with the scene and hierarchy view in full screen, and I noticed something interesting after clicking on the object in the hierarchy and moving the object in the scene view:
Unfortunately my PrintScreen doesnt show the actual mouse, but as you can see the scene view acts as though I'm clicking on the object, but here at the same time I saw my real mouse off down to the right! Also while I've selected an object on the scene editor and I move my mouse off the scene window things get a bit off and the mouse will pop up on other sides of the window and so on. I don't know if that's normal and its that way for everyone or if it's just me and it might help figure out what's going on.
Man I've really been liking Unity but if this keeps up I think I'll have to drop it and find another software, because I certainly will never be able to design anything worth while if I have to select the object on the hierarchy every time for every single object.
Some bug for me on Mac platform. I resolve just entering and exit from fullscreen mode.
Probably may also work change layout with top-right combo.
I had similar issue while using older versions of unity (in addition inspector window lost the focus repeatedly). In my case rearraging editor windows and saving custom window layout solved it. As far as I remember, I just moved scene view outside Unity window (on the second screen) as well as hierarchy view, and saved resulting position as a new window layout.
Not sure if there is anything else I can tell about it, it's pretty mysterious problem.
I'm overwhelmed with joy right now!! The problem was indeed a bug. I was working on a project and moving objects around (still using the hierarchy to select objects) and then a split second later for absolutely no reason Unity decided to start working the way it should've!!! I guess its just one of those issues where you just have to cross your fingers and hope it'll resolve itself. I'm so glad this dumb issue resolved itself because I was about to tear my hair out and succumb to using another computer for my unity design, or even worse another software. Thank you to everyone who helped!
I've a project which is a randomizer. The randomizer gives a random number (of course) which is used to call a random game.
For now, I only have one game.
When I run the randomizer to get the game, everything works and it loads the game flawlessly.
But, when I close the window which was created for the random game, it also closes the parent window which gives the user access to the randomizer.
I am not sure as to why this is happening.
I tried refactoring the name of my shell as well as my display, wondering if this closing was occurring because they shared names, but that didn't fix anything.
I'm not sure why this is happening or what code would prevent this from happening.
Any thoughts would be much appreciated!
Thanks!
Nathan
The issue was that there was a JFrame invoking frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);. This was forcing all windows closed. Turning this off fixed the issue.
I have just been enlightened on what I previously thought was a short-coming of the whole Mac OS X platform - that like Windows, a user may select a block of text and drag it. This is particularly useful in developing.
However, the reason I thought it wasn't an available option was because it has never worked for me. No programs allow for select and drag, and I've gone through several online tutorials and forums to see if anybody else has the same issue. None of my work-mates can figure it out.
Why would my whole system dis-allow text dragging? Now that I know it's possible, it's driving me crazy not being able to do it.
I've gone through the System Preferences and the Mouse panel has no specific drag option. Trackpad has a single-finger drag option, but that's not allowing dragging, even with the trackpad.
I'm on a Macbook Pro, from around 2008. I'm using an external mouse and running OS 10.6.
This should probably be on apple.stackexchange.com instead of here, but be that as it may... the trick is that you need to hold the mouse down for a fraction of a second, until the mouse cursor changes from an insertion point to an arrow, and then you can drag.
I already asked this questions over at Ask Ubunutu. Unfortunately I have not received an answer. As this question is not Ubunutu specific, I am trying it here.
I am using xrandr via console to enable/disable secondary monitors. This work fine so far. Unfortuantely if I move my mouse beyond one screen, it appears on the other one. How can I disable this feature - and lock the mouse to one screen?
I use Ubunutu 10.10 and awesome - no gnome/kde.
I've never seen anything in the Xrandr or Xinerama docs about restricting mouse movement to a single monitor.
And, before Xinerama, I used to run multiple X screens on multiple monitors, but the mouse moved freely between the monitors without trouble. (Windows were stuck on the monitor they started on; it worked much better than it sounds. :) So that's probably out.
You may be able to solve this starting another X server. Configure the second X11 for the correct screen, no mouse (keyboard too?) input device, and start clients on that second X server using DISPLAY=:1 xterm & and so forth.