We've received the new Microsoft Surface v2 this week, and I've done something such that it broken the Surface Mode.
What should happen
I could double-tap the shortcut to Enter Surface Mode, say ok to the dialogs that popped up, and it would take me to the SurfaceLoader (a program that just shows a ring of particles pulsing in an out of the center). After a moment, the water-simulation Attract program would pop-up, where I could touch the center surface logo to see the list of registered Surface programs.
What happens instead
I double-tap the shortcut to Enter Surface Mode (turning on debugging), and nothing comes up past SurfaceLoader. It seems that the other programs are running, but SurfaceLoader is aggressively maintaining focus.
What might have messed things up
Installed my Surface 1 Application
Made my Surface 1 Application run on startup
Installed Surface SDK Samples
(Maybe) accidentally moved an important file elsewhere - (just because its so easy to accidentally moving things on the Surface in Windows 7 Touch.)
Let's go over each of these.
For my Surface 1 Application, built in XNA using the Surface 1 SDK, we used an .msi installer to install the program. It ran, but being that Surface 1 is built around a small program called SurfaceInput.exe running in the background, the program did not respond to input. The program was run at startup through a registry key.
I have uninstalled the program through the control panel (double check this)
I have double-checked the registry to make sure the keys are not still there
For the Surface SDK Samples, I got them from the Microsoft Surface 2 SDK at: http://www.microsoft.com/download/en/details.aspx?id=26716. After installing the SDK, I navigated (on the Surface) to C:/Program Files (x86)/Microsoft SDKs/Surface/v2.0/Samples/Surface Code Samples.zip. I extracted the zipped files, and installed them with InstallSamples.bat. Installation succeeded normally.
At some point, I was able to see a list of these in the Surface Application Launcher screen. I can no longer get to that point, so I'm unable to exactly recreate my steps.
I'm not sure where these examples extract to - the placement does not seem to be contained in InstallSamples.bat file, and I cannot find them with Windows Search. Perhaps they are built in the same folder and merely registered elsewhere with the Surface, but since then I have done a series of System Backups. When examining the Surface Configuration Editor, BingSurface is the only Application registered with it, leading me to believe these are probably not the cause.
Finally I may have accidentally moved some arbitrary file to some other directory. This does sound rather horrible of me, and while I don't recall an instance where I've done this, it is incredibly easy to accidentally move a file or folder when Surface is in Windows 7 Touch mode. Even while writing this, I somehow moved the taskbar from the bottom of the screen to the top of the screen while it was locked with just two touches. I don't think this is the problem, but its easy enough to do that I can't rule it out either.
To remedy this, I have tried Windows System Restore. I was able to restore to a point after installing my Surface 1 app, but I have tried twice to Restore to the original state of the surface without success. I waited 10-20 minutes for System Restore to show progress, and both times it stayed on the Initializing screen. It was not graphically frozen, as the Windows loading circle was spinning, but from my previous experiences 20 minutes seemed to be way too long for this process to be going correctly.
Things that do not work
Running Enter Surface Mode w/ debugging - eternal loading screen. Can alt+tab to see Attract is running, but does not switch focus to Attract window. Can hear the sounds of Attract play when I touch the surface on the loading window.
Running Surface Shell - eternal loading screen. Can hear the sounds of attract play.
Running Enter Surface Mode w/ debugging in Single Application Mode set to SurfaceBing - eternal loading screen. Alt+tab reveals its running, but does not switch focus to bing window.
Running Surface Shell in Single Application Mode set to SurfaceBing - eternal loading screen. Alt+tab reveals its running, but does not switch focus to bing window.
Running Surface Loader - running it directly causes same problems as above.
Things that do work
Compiled Sample Project RawImageVisualizer on separate system - runs great on the surface. Can see what the pixelsense is seeing.
Launching Bing for Microsoft Windows Directly - works just as it should
Launching Attract directly from C:\Program Files (x86)\Microsoft Surface\v2.0\Attract - watery program comes up just as it should.
Environment Lighting Optimizer - works totally fine.
It seems like something happened to SurfaceLoader, such that it thinks it should always be on top of everything. I shall give System Restore another go, allowing it a full hour. I will also double-check the properties of SurfaceLoader to make sure it doesn't have anything akin to "run on top" checked.
I know Surface 2 is new, but I would greatly appreciate any tips you have.
You've probably figured it out by now, but for posterity's sake, I'm guessing you didn't have permissions set correctly. You should always run the Surface Shell/Enter Surface Mode as Administrator or set the properties to always run as admin. Your own programs always need high level permission. If you don't run as admin, it seems to raise the alert window you get when Windows7 asks for higher level permissions but you never see it. It just waits and waits. "Surface Mode" is actually just a special user that's hidden until you enter it and never runs Windows Explorer or shows the desktop. So you have to deal with Windows 7 permissions to have programs run for both users. Hope that helps!
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.
I'm new to scratch.
I have this code within a sprite, which works as expected without noticeable lags:
But, when I "export" the flickering into the 'flicker' block, it has a very nasty lag:
I created a special sprite in order to easily "feel" the lag, with this code:
This ball smoothly moves, until (every 5 seconds) there is the flickering effect and it stops for 1 second or so.
Can anyone give me a clue why it happens, and how to prevent it?
The project page is here.
Any assistance would be appreciated.
Let me start by pointing out that the problem does not occur when I launch your project.
I tried it in 5 different web browsers on 3 different devices with 2 different operating systems, and every time, the ball just kept moving.
However, I can make such an issue happen by enabling 'Run without screen refresh' in the 'flicker' block, as follows:
Right-click on the red 'define flicker' block.
From the context menu, select 'Edit'.
In the 'make a block' dialog, turn on checkbox 'Run without screen refresh', then click OK.
I suspect 'Run without screen refresh' claims all processing power, effectively blocking any other (concurrent) scripts.
My guess is, you already fixed the problem yourself by turning off 'Run without screen refresh'.
In general, 'Run without screen refresh' is a great way to reduce lag in scripts where speed is essential. But never use it in a script with 'wait' or 'forever' blocks, or it will cause lag.
I had a GUI made using GUIDE. Suddenly when I reopened MATLAB the GUI window got resized, zoomed-in and cropped, missing the top of it. This shows in GUIDE itself as well.
I'm using the same computer and MATLAB version. I already tried to restart MATLAB and the computer itself.
The only thing I can think of that changed is a second monitor I was using, but I tried plugging it in and out, and it didn't help.
This doesn't happen in other GUIs I'm using.
Specs:
Windows 8, MATLAB R2013a, 1920x1080 screen resolution.
Try changing the units of all the controls to normalized.
MATLAB sizes GUIs based on system information about the size of the screen, so adding a second monitor could change that system information and confuse MATLAB. You could test if that is what caused the problem by unplugging the new monitor and restarting the computer/program.
For one project I had to change the units on everything to characters so that it would size appropriately for various screen sizes. Normalized should work too, however, it won't revert the gui to how it was before it got jacked up, only keep it from changing again.
So, try reverting to your original screen configuration and restarting the computer. If that resolves the problem, change your units to normalized or characters.
I'm fairly new to AHK, but have already done some research on this and haven't found a good answer. I would like to be able to launch an application maximized on a specific monitor. I think the current best practice is to Run the app and then use WinMove to position.
Currently I have a three panels in the following configuration: Left (1680x1050), Middle (1920x1080), Right (1920x1080).
The logic to Run and WinMove seems straightforward, but since I have different resolutions and I would like to Run the apps maximized I'm at a loss for how to script this out.
Any suggestions?
Yeah, thats about right.
What I would do is Run, then WinMove horizontally to the correct monitor, then WinMaximize
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.