This might be esoteric but here goes.
I'm developing a program in WPF for use on a multitouch screen. I'm using the Surface 2.0 SDK and trying to get the Toolkit to simulate inputs and run the stress test. However SurfaceStress.exe is throwing an error:
Error 0: Cannot get reference to virtual digitizer controller.
and Input Simulator is giving me a timeout error looking for the controller.
I've read up about it on MSDN http://msdn.microsoft.com/en-us/library/ff727911.aspx
I know it can't run two controllers at the same time and it's not on a SUR40. It says "Tablet PC Settings" would only appear if the Input Simulator is running. But it's running anyway and its Setup button is grayed out. I don't have a touchscreen but I do have a Wacom Bamboo tablet connected. Has anyone else had interference between a tablet and Surface Input Simulator?
It was in Device Manager. Bamboo touch drivers disabled the Virtual Digitizer Controller which was also listed as a device. Flip the switches and rode off into the sunset. good job, me! o/
Related
enter image description here
System UI is not responding when I lunch android emulator and after clicking on close app it is very slow to use.
My system Specs ->
POP OS (Ubuntu)
8GB Ram
i5 7th gen
Nvidia 940mx
Quick Resolution:
Click on your AVD manager
Select your Emulator and click the edit button for your device.
Choose Wipe in the drop down menu.
See illustration below ..
Recommended Resolution :
Click on the AVD manager .
Select your Emulator and click the edit button for your device.
Select Hardware in the Graphics drop down menu.
For more information on Graphics acceleration see Android Studio Developer Guide
Just go to your AVD manager and click the Down arrow i.e DropDown Icon in the far left where your emulator name is displayed and Do a cold boot but make sure you are not running your device when doing it. It works for me for sometime say for 3-4 hours then I need to do it again I m not able to find the permanent solution to this but it is rather better than wiping down the data which would not work if you are a mobile dev as it would delete the apk it has installed and all that stuff. I hope your problem is resolved. If any of you seeing this comment in future I mean in 2025? Please reply me to see if I m alive! Bye
If you are using a 64-bit operating system on your computer, you should change emulators architecture(CPU/ABI) from x86 to x86_64. Create a virtual device and choose a system image like this one
The problem
Can I get the current running camera instance and and give a particular file as input in IOS Real Device
Is this possible with appium ?
Please Advise
More Details:
I am trying to feed my camera an image during runtime. So basically my application has a feature: search a product by scanning a barcode, Since I am trying to automate this, I want to provide an image with barcode and have camera take that image while scanning.
Environment
Appium version: 1.3.2
Desktop OS/version used to run Appium: MAC OS High Sierra (10.13.4)
Mobile platform/version under test: iPhone 8 Plus, OS 11.3
Real device or emulator/simulator: REAL DEVICE
Please Advise
Appium is a black-box testing framework, so it cannot set image for your app directly in the runtime.
However, Appium exposes push_file functionality that places a file onto the device in a particular place.
For iOS it works only on Simulators (running Xcode SDK 8.1+)
driver.pushFile(
"/path/to/device/image.jpg",
new File("/Users/dev/files/image.jpg")
);
If your app supports image selection from gallery, you can push file and then select it in the gallery.
In case it doesn't work, you may look into writing tests directly using XCTest/XCUITest framework
I have a Metal-powered app that works just fine on my dev Mac, my main Mac and my friend's Mac. However when I send it to Apple, they get this awful glitch while resizing window. Here are their screenshots:
What on the Earth can cause that only on their macs?
Edit: I was able to retrieve system info from Apple engineers.
So I guess the problem is with either NVidia driver or non-Retina screen. Any thoughts on that?
After enabling native debuging i am able to see where this is giving error. in CCGLProgram haveprogram function. It builds fine only while running on the device it gives this error. Also the shaders are precompiled for wp8 so I dont know why this problems exists.I am running it on my desktop and running on my nokia 820. The same works fine on my laptop on a simulator.
vshaderByteArray and fshaderbyteArray get a different value every time. I wanted to attach an image but it seems I need 50 reputation. So adding link below.
http://discuss.cocos2d-x.org/t/wp8-xaml-version-3-2-gl-program-error/15679
The emulator used to run fine, but as of late whenever i try to launch it, whether directly from the programs list or by running code in Visual Studio, the emulator will launch, stop responding and crash, then when I hit "close program" it will launch itself again, stop responding and crash again. I've looked everywhere and cannot get an answer to this issue.
Thanks
The only way i think is by reinstalling the product.
Just so you know, make sure that you're using the right version of the SDK for your OS (on PC) and using just the right emulator supported by your OS (pc).
Like for SDK 8.0, if you're developing Win8 app, use 'Device' for direct app deployment onto your phone or "Emulator WVGA 512MB" for optimized, memory-constrained output on your PC itself.