I'm using a program called desklock which closes explorer/desktop and blocks hotkeys so that a user can only start programs by buttons on a small window. This will be going in as a touch-screen only HMI system, so I need to be able to launch the on-screen-keyboard. I have a button on the window for this, but whenever I try it, I'm always given the error, simply "could not start on screen keyboard" I've tried launching osk.exe directly, launching a shortcut to it, and launching a script to start it. All three methods work standalone, but when launched by this button, nothing works
If you O.S is a 64bit and you are trying to launch osk.exe from a 32bit application you might experience this problem.
This sould be caused by the File System Redirector which redirects calls to C:\Windows\System32 to C:\Windows\SysWow64.
I have the same problem with the osk.exe in C:\Windows\SysWow64 on Win10.
Related
I mainly run Cypress and Chrome through WSL2, whenever I try and make any of the windows that open full screen a part of them always displays on my second monitor.
Is there anything I can change in a config file or something to fix it?
I don't know if it's related but the cursor on the WSL2 GUI programs is huge. Is this something that can be fixed too?
I am trying to set up the Divio app on Win10 Pro.
I can launch the application, log in, select the workspace folder for my project, so the required dependencies should be fine.
However when I click on "Set up my project", then a new window is opened with a text "Preparing logs...", and an animated "hour-glass" appears next to the "Open Shell" button in the lower-left corner, but that's it. Everything hangs up at this point, and I can't figure out what's wrong. Restarted the computer and the app several times, but with same results.
Any ideas how to work out what is going wrong?
The Divio app is an Electron application, and uses Chromium for the interface.
You can invoke its Inspector as you would in Chrome itself, using command-option-i on Macintosh and control-shift-i on Linux and Windows.
The Inspector's Console tab will show any errors, and this will help understand what is happening internally. Typically, they will be errors related to the operating system in some way.
I am running one .NET binary using mono on my Linux platform PC and it is working fine on process startup.
But when i moved my running GUI window to another window and get back to that windows at that time , My GUI Application goes into the hang state because i can not press any button on My GUI window.
I have also used all the optimization option step by step while running .NET binary using mono but still causes the GUI hang issue.
I have debug my .NET binary with some debugging options and found that whenever GUI window application goes into stuck condition at that GDIplus library code is running. so, it seems that there is something is going wrong into the GDIplus library.
does any one have idea what is happening here or any one have faced this issue before?
Please let me know if anyone need any more information and give valuable feedback as sson as possible.
I just installed evans debugger and when i click the program it never opens. im running suse linux 11.1.The program installs fine and shows up in my menu but never opens
Try to debug it the naïve way:
Open up Terminal.
Find the name of the executable that links to your debugger (editing the menu entry might show you the command that is run when you click on the menu item).
Run this command via Terminal.
Post the output so that we can actually see what's making the program not work.
I have a question regarding Visual C++. While executing a Visual c++ project file, the application runs and along with that, a command window gets opened. It normally disappears as soon as the application running is done. I am not sure if that command window could be avoided when the application runs.
Thanks,
Krishna
Win32 executables must be either a command line application or a GUI application.
If your EXE is a command line application and it is executed from a command line then no extra window is created.
If your EXE is a command line application and it is executed from a GUI application then a new console window will be created for it.
If your EXE is a GUI application then it's up to you to create whatever window(s) you want.
Check how your application is being compiled and then make the right decision for your app. In Visual Studio follow these steps:
In Solution Explorer right-click on the VC++ project node and choose Properties
Navigate to: Configuration Properties / Linker / System
Check the value of the "SubSystem" property
Two of the SubSystem options are Windows and Console, and these describe the two settings I mention earlier.
More information about this GUI vs. Command Line behavior is available on these links:
How do I write a program that can be run either as a console or a GUI application?
Program both as Console and GUI