(Windows) MonoDevelop (2.8.8.4) freezes when creating new NME solution about md-haxebinding

[jgranick]

Does this still occur?

It creates the NME solution after some time waiting (about 30secs on a quad core machine).
Tested it on win7 32bt and MacOS Lion.

While creating solution on windows it blocks the UI with not responding message in the form title bar but
after ~30sec wait it finally creates the solution.

Building simple trace("foo") solution works ( html target ) but no code completion (posted as new issue).

[andyli]

It is also affecting me on my Mac 10.7, using MonoDevelop 3.0.3.4, Haxe Language Binding 0.3.1.

Try waiting a little bit longer. It takes some time unfortunately. At least for me.

Sent from my iPhone

On Jul 19, 2012, at 9:48 PM, Andy Li [email protected] wrote:

It is also affecting me on my Mac 10.7, using MonoDevelop 3.0.3.4, Haxe Language Binding 0.3.1.

---

Reply to this email directly or view it on GitHub:
#7 (comment)

[andyli]

Yes it does create the project after some time.
What I meant is it also freezes for several sounds when creating project.
And I believe it shouldn't have take that long.

[jgranick]

I'm not sure why this happens.

I'll try and profile it and figure it out

------Original Message------
From: Andy Li
To: Joshua Granick
Subject: Re: md-haxebinding MonoDevelop (2.8.8.4) freezes when creating new NME solution (#7)
Sent: Jul 19, 2012 2:01 PM

Yes it does create the project after some time.
What I meant is it also freezes for several sounds when creating project.
And I believe it shouldn't have take that long.

---

Reply to this email directly or view it on GitHub:
#7 (comment)

Sent via BlackBerry by AT&T

[MatthieuChardon]

I've the same issue, even with the "Run as administrator" option. But for me, it never creates a valid project. All what i get is an empty folder : "Assets".

Windows 7 64bit, MonoDevelop 3.0.3.5, Haxe Language Binding 0.3.6.

EDIT : Finally, it succeeded ! I just restarted my PC. Now, i just have to wait something like 30sec.

[jgranick]

I cannot reproduce this problem using the current alpha. I'm not sure if this was because of the move to a standard "project.nmml" file, or if this was an error that was corrected within the IDE, but I believe this is resolved.