I successfully created a prototype for my RPG game. But I experienced something strange, no errors are showing, everything "works" as it should, but when I try to run the program, nothing opens. It just gets stuck at debugging.... I can´t find any help anywhere, even my professors don´t know. Have a look at the screenshot. ..
Related
I wanted to test Three.js for a new project and imported it together with some example code.
In Firefox however the canvas with the three.js stuff doesn't show up and I get the error & warnings that you can see beneath. I guess the warnings appear because the WebGL context was not created correctly in the first place however I don't know what would go wrong there.
I don't know what could be the problem as the code runs fine and without warnings/errors in Chrome.
Both browsers were tested on an openSuse machine if that could play a role.
Thanks you for any hints on what could be wrong here!
I have this win32 application. I created an installer for it and in my computer it works perfectly fine. I can install and run it. However, when someone I know tried installing it, the application ran but with user interface issues. This is how it looked like. I didn't add the white boxes nor the weird lines. Does anyone of you know the reason why this happened? I have no clue at all T_T. Is there a way to prevent this from happening again? By the way, the UI was made using cocos studio. I'm using cocos2d-x for this app.
Im building a Unity game for windows and mac.
They both have the same codebase and little to nothing changes between the Windows and OSX versions of the game.
On OSX every time I quit the game it gives me a "Do you really want to quit?" message which is presented to the user before "OnApplicationQuit" is even called in any script..
I want to get rid of this message, If I want to display a message for quit it would definitely be a better message than "Do you really want to quit?"
Has anyone else come across this issue and is there some way to fix it ??
Thanks for any help.
UPDATE
the only thing I have found to override this is a native plugin to override the window close event and send -[NSApplication terminate:] instead. Which may work for my needs right now, but it is likely to create a whole new avenue of issues later on.
I've been tasked with adding gesture support to our product which was simple enough on a new Windows 8 machine - I just added WM_GESTURE to our wndproc and everything worked as expected. However, when it came to getting it to work on a Win7 machine things have been very different. I receive no gesture messages at all. Even spy++ shows no gesture messages being sent to my application. I've managed to get touch messages working using RegisterTouchWindow() but I know that I won't get an gesture messages when touch is disabled, so that was only done for test purposes. I read somewhere that "flicks" can interfere, so I have disabled flicks, both from the control panel, and from code using SetOpt(). I've even tried hooking in to GetMessage using SetWindowsHookEx. Nothing I do works. I've tried the example programs from the Microsoft Touch Pack, and gestures appear to be working there, in that everything works as expected. I've read all the documentation I can find, and still can't work out what's going wrong. Can anyone provide any more insight into this? I feel like it should "just work", but it really isn't!
Thanks in advance.
My wp7 app crashes when I come back from a task such as Map, Call or Web Browser. Infact, if i lock my phone and resume it again, still it crashes. Please tell me what could be the problem and how can I remove it?
There is a problem with you code.
Remove the application off the phone by starting a new emulator instance.
Open App.xaml.cs
Put a breakpoint in the method RootFrame_NavigationFailed and Application_UnhandledException
Now use the CallStack to find the root of the issue.
With no code posted (and in your case it could be ANYTHING in the project) you will be the best person to resolve your issue. If you can post a small reproduction on here we can take a look.
In application exit methods you probably should restore the data you dealt with last time before you quited