Compile errors after moving dialog folders up/down in 3.3.0

Started by AGD2, Tue 01/04/2014 11:00:37

Previous topic - Next topic

Crimson Wizard

#20
Quote from: AGD2 on Sun 06/04/2014 21:15:34
Ah, right. Would this be something for 3.3.1, then?
If someone will make this...
I don't know, at this point this looks like a serious change to engine.

AGD2

I was in the process of changing all my Dialog.Start(); instances over to goto-dialog instances when the editor crashed with the following error:

Spoiler

Application Error
---------------------------
An unexpected error occurred. See below for details.

System.ComponentModel.Win32Exception: Error creating window handle.
   at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp)
   at System.Windows.Forms.Control.CreateHandle()
   at System.Windows.Forms.ToolStripDropDown.CreateHandle()
   at System.Windows.Forms.Control.get_Handle()
   at System.Windows.Forms.ToolStripManager.ModalMenuFilter.PreFilterMessage(Message& m)
   at System.Windows.Forms.Application.ThreadContext.ProcessFilters(MSG& msg, Boolean& modified)
   at System.Windows.Forms.Application.ThreadContext.PreTranslateMessage(MSG& msg)
   at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FPreTranslateMessage(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(Form mainForm)
   at AGS.Editor.GUIController.StartGUI(String[] commandLineArguments)
   at AGS.Editor.ApplicationController.StartGUI(String[] commandLineArguments)
   at AGS.Editor.Program.RunApplication(String[] args)
[close]

I guess this could be related the the same issues mentioned previously in this thread. I did notice (when I reloaded the game into the editor) that I had accidentally doubled up a dialog with two commands under @2, like this:

DBortInitiation
Code: ags
// Dialog script file
@S  // Dialog startup entry point
return
@1
  cBort.Say("Blah Blah Blah.");
return
@2
goto-dialog dBortMain
 dBortInitiation.Start();


Not sure if that has anything to do with it. Just mentioning it in case it's relevant.

I had saved the game (CTRL+S) but hadn't compiled it when the crash occurred. After saving, I recall trying to double-click several dialog topics, and none of them would open. After a few attempts, I double-clicked another dialog and the editor crashed with the above message.



tzachs

Quote from: AGD2 on Mon 07/04/2014 08:42:06
I was in the process of changing all my Dialog.Start(); instances over to goto-dialog instances when the editor crashed with the following error:
The "Error creating window handle" exception can happen when you go out of resources. This could be a resource leak somewhere in the system, but this could also be due to too many open windows.
Did you have a lot of open windows in AGS?
Did you have a lot of open windows outside of AGS?

AGD2

I didn't have that many windows open in Windows nor many tabs open in AGS at the time. Actually, far less than I typically do, as I had just loaded up the editor not long before.

HandsFree

Don't know if this goes here, but I'm using 3.3.0.1156 and my game exe is deleted everytime I use F5 or ctrl-F5. Is that expected behaviour?
I used the winsetup to specify full screen so ctrl-F5 would give me a full screen. Is there another way to achieve that (ctrl-F5 now gives me a window)?

thanks

edit: oops, this was meant to go in the AGS 3.3.0 thread. Apparently I ended up in the wrong thread...

Crimson Wizard

#25
Quote from: HandsFree on Fri 02/05/2014 14:13:28
Don't know if this goes here, but I'm using 3.3.0.1156 and my game exe is deleted everytime I use F5 or ctrl-F5. Is that expected behaviour?
I think it worked like that since 3.2.1, at least. It may be argued if this is a right thing to do...

Quote from: HandsFree on Fri 02/05/2014 14:13:28
I used the winsetup to specify full screen so ctrl-F5 would give me a full screen. Is there another way to achieve that (ctrl-F5 now gives me a window)?

Go to File -> Preferences. On preferences window set "When running without debugger" to "Use game setup configuration".

HandsFree

Thanks that works.

I used 3.2.1 before this and I'm sure I didn't lose any executables. It looks to me it happens since 3.3.0.

monkey0506

HandsFree, I'm reasonably certain that running with the debugger has deleted the executable from the Compiled folder since 3.0 was first introduced.


SMF spam blocked by CleanTalk