I'm currently writing a Snake in C++/ncurses, and my Ctrl+C has suddenly stopped working when inside the game. The fun thing, tho, is it still works outside of it (so when I'm just in the terminal) and it ALSO WORKS when I compile the code on another laptop.
It's just this pc that encountered this issue. Randomly.
What could it be?
Checked terminal settings and reverted code changes.
Tried using different terminals.
Related
I'm working on a project with two windows, one displays on a TV and the other on a tablet (not duplicate screens). It's an interactive game for kids. When I run within processing it works flawlessly, takes a while to load tho. But when I make an exe file (tried w/ and w/o fullscreen and 64/32 bit) it still starts the loading screen but then stays stuck on the loading screen forever. Anyone have any suggestions as to what might be the issue?
I currently run a 64bit Windows 10 development box. I have old VB6 source that I have to unfortunately keep updated for the time being. For some reason all the sudden I noticed that one of the applications I have just built seemed to stay running in the background after the GUI was closed.
I started debugging the issue more and more until I found out that the only time it would seem to persistently stay open in the background after the GUI was closed was if I clicked the button on my form that would call the Common Dialog control to show the file open GUI. I only have to show the file open window and then hit cancel for this to happen.
This ONLY seems to happen on ONE of my dev machines (not the other). Every time I use that CD file open box I have to open task manager up and end the task. I also tried to make sure all forms were closed when my main form starts to Unload. Nothing seems to work or shed any clue on what the issue is. I have also double checked that the following files are now all the same coping them from the known working dev machine to my broken one and re-registering them.
COMDLG32.OCX
comdlg32.oca
comdlg32.dll
COMDLG32.DEP
Both machines are running the same exact OS Win10 Pro 64bit.
That does sound strange, getting different results on the two machines. Pragmatically, you can work around the problem (without actually understanding it) by making sure that you execute an End statement. (You can put it in the QueryUnload event to make sure it's hit if the user clicks the "X".)
I have written an app for OSX (Sierra) in Go (lang) with the GUI powered by the Golang QT binding therecipe/qt. When I build the app and run it from the command prompt with command open $(pwd)/myapp.app I get a terminal output while its running, and everything works fine.
When I double click on the app in finder to run it, I obviously don't have access to the console to see debugging, but in parts of the app that work fine in the GUI when I run from console (clicking on things, etc), it crashes the app when run by clicking on it.
I realise people don't know what the app is, and without seeing where in the app it crashes, they can't help me. What I am after is some ideas about debugging it, for instance:
Outputting logs to a text file and tailing the text file to watch as it is written to
Connecting a debugger to the application by the process, perhaps I can discover where it crashes. This doesn't sound straight forward
Is there a way to attach to a console of an application run like this to see what it is outputting?
Any ideas appreciated.
Thanks
I cannot work any more with Intellij Idea, under OSX. After performing an IDE upgrade, the IDE main window (and any dialogs) has stopped responding to mouse clicks. The menu still works.
I have tried setting the log level to trace, with no success in getting any information of a possible exception when reacting to a mouse click.
The system is generating some thread dumps (a lot more under 2016.2, I have now downgraded to 2016.1.4). Is there a way to get more information to diagnose this issue?
I had a similar issue. It turned out it was my mouse (Microsoft Sculpt wireless) that was causing the issue. After plugging it out and using the touchpad, it suddenly started working. The issue is not 100% reproducible, though. It sometimes works fine, sometimes doesn't
Upgrading OS X helped once, but then the problem came back. Updating IntelliJ and even reinstalling it with removing all data never helped.
#edit: I borrowed an identical Microsoft Sculpt Desktop set from my friend - it worked fine. I bought another one for myself, and so far it works (it's been 3 months now). Weird indeed.
I let me Parallels Desktop running Windows XP to start automatically during mac log-in. And to start Windows upon launch to let my dad use his WinXP by just pressing the power button, bypassing the Mac login window and desktop completely. When he shuts down Windows, Parallels closes.
I seem to remember I have a trigger to shut down mac as soon as Parallels closes. But I don't remember where... I have an AppleScript that tells Finder to shut down. I understand that. But now the problem is Mac shuts down AS SOON AS it boots up every time! I can't figure out what's triggering the shutdown... And I've run out of places to look.
It seems like a normal shut down rather than a fatal error. Seems like someone has chosen the 'Shut Down' command as soon as Mac starts up. So could mac gurus suggest places I should look -- what might have triggered this -- I'm pretty sure it's Parallels-related. Maybe there is something in the Package Contents linked to the shutdown script??
You added the Applescript (that shut down the mac) to login items