r53 is released now, is it any better?
Develop games in your browser. Powerful, performant & highly capable.
Does the exported project work OK if you ignore this error? I think it might be a false positive, so I'll disable the message for the next build. I'm just preparing the new build now, it should be out in an hour or so.
Ah, good tip! OK, fixed in next build.
Hm... well, we'll see what happens with the next build and go from there, otherwise we might enter the realm of telepathic debugging.
I think attention to detail is important in Construct 2 to ensure using it is a good experience. So I do want to fix small issues like this where possible - it's just in this case, it doesn't look like it's possible. (The code says "Maximize box: disabled" etc. so no idea why XP still enables the option.)
Ah, I see, got it. Thanks, fixed for next build. It would have waited for you to "finish" the current frame (i.e. switch to another frame or close and reopen) before the preview updated - now the preview is always up to date.
Hmm, not sure what else I can do to tell Windows those aren't meant to be enabled. I think I might leave this as 'won't fix' - Windows 7 gets it right so maybe it's a bug in XP.
Thanks, should be fixed in next build.
In the context menu for me (Windows 7) both minimize and maximize are disabled. What OS are you on?
I double checked the code, and both dialogs also specify that maximize and minimize are disabled in the dialog designer. So I'm not sure where the options would be coming from if you see them.
I'm not sure what you mean - if I insert a new sprite and immediately preview the default animation, I get a blank white 200x200 window (the size of the default canvas). That's the intended behavior. What do you see and what were you expecting instead?
Yep, suppose you have 5 conditions and you want to see how things run with one of those temporarily disabled. Instead of having to delete it you can toggle individual conditions, just like you can toggle individual actions, or entire events.
I've made a possible fix for the next build - it was to do with the HTTP server shutting down. It should be out in a day or two. When it comes, let me know if that fixes it!
You've only disabled the condition, so it acts like an empty event with an action. Empty events always run, so yes, this is intentional.
If you right click the event margin on the left and disable from there, you can disable the entire event.
Can I ask if there's any particular reason you're holding back from staying up to date with r52? Newer builds often have important bug fixes.
I'll double check the code for when C2 shuts down and see if I spot anything.
You do not have permission to view this post