GAH. IT KEEPS HAPPENING. So frustrating....

Perhaps if the save mechanism changed... for example, instead of trying to save an auto-backup file as the >same< name... you save it as backup2, and if that succeeds... then replace backup1?

It may seem easy to just close google drive\drop box first... but sometimes you forget to do that - and in all honesty, you shouldn't need to.

Blah....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

Can't be any more help, other than to say this plugin has a pretty big performance leak. All I did was left the demo you have running for a couple hours, came back, and it was running at 10fps from 60fps.... turned it off, then back on again, and it was fine. Perhaps it was a fluke? I'll do it again tonight before I go to bed... to see where it's at in the morning.

I'm trying to find out if a user is typing in for example, the wrong number in the property list... and if they do, alert them of the wrong thing.... problem is, I don't see anything in the array that will allow me to pull the current value. Is there a way?

All I see: [type,name,initial_value,description,param]

Is there a way? I even tried a number of things in the "OnPropertyChanged" function... but there's nothing in there either.

Thanks!

Fixed - I meant to put unlisted.... didn't want anyone searching for a C2 on youtube to display a bug.

I just upgraded to 194.2 and recorded this video:

I'm using Windows 7, 64-bit with Construct2 r194 64bit.

I'll get a vid together to show ya.

Ok, I think I found out the problem. Try uisng this utility, it's a pretty good open source one.. I just drag my file into the app, and it locks it until you close it:

http://www.jensscheffler.de/filelocker

Either way, I tested a bunch of times, and was able to get it to save without freezing... and the only way, was using the default .capx type project.... this issue does NOT happen on capx files.... those work 100% fine for some reason. This bug only occurs when you have your project saved as a caproj, which unfortunately is how I always work.

If you'd like, I can provide a video capture of the bug? I literally do this:

-File new

-Add sprite

-Save As Project

-Move Sprite

-Save

Lock .backup1 file

-Move Sprite

-Save

And this is where it hangs. Let me know. <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

Strange... cause I just tried it again with 194, and it's the same thing.... here are my steps exactly:

-Open any project then save

-Make a small change, and save again so that the backup1 file gets created

-Right click on backup1 in explorer, go to add to archive and start archiving the file... pause while it's accessing the backup1 file... my pause happened at 10%, but I really don't think it matters.

-Go back to C2, make another small change, and then just press CTRL+S. It'll sit at the "Saving..." screen permanently.... no way of getting out of this.

Perhaps one way would be a cancel, or a close window option on the saving screen, to cancel the save in progress? Just a thought.... that would get rid of this issue anyway... and other problems when you press save by accident for example.

I meant styles - I never use them so don't pay attention to what they are called:

[attachment=0:1s9u15f4][/attachment:1s9u15f4]

You could try changing these around and see if you get the nice tabs back (the choice shown sure has them).

Touche... they're there. Why the default changed is beyond me... but glad to see them there. Thanks buddy.

If I'm not mistaken these are the tabs that come with the visual style you have chosen - previously they were always the base one, ignoring the style or something like that, so that was considered a bug and fixed in r193: "Editor should be better at remembering the selected theme's tab style after restarting"

Or perhaps this is a side effect of that fix.

I've never changed the tab style, theme, or anything in C2. It always installed by default on every machine I've installed it on with the colored tabs. NOW when I install, even on a fresh machine, or one that has always had color, it does these crumby grey ones... and I can't revert to anything else unless I go back to 192... which I'm considering now... I've tried every different "color theme" and that only seems to change the colors of the event sheets.... not the actual tabs. Workflow is being crippled because of this... quite a shame. I'm used to ALT+1, ALT+2, etc to switch between tabs in other programs, but because that feature does not exist in C2, I was forced to get used to colors.... now with those gone, I have absolutely nothing.

Check out the differences:

I want to hit my head against the wall... the new ones, although sleek, really blend into the background, and lose functionability. If anything, what should have happened, is all event sheets be lined green, and all the layout sheets be solid green.... at the most! For them to lose color completely, really makes it difficult to quickly determine which one you were working on when they have for example, the same names.

"Purple is the event sheet for the one I'm working on.... Pink is the one I'm going to"

For example is how it used to work.... NOW I have to remember positions, which can change at times... and when you see two with the same name, like in the example, you end up clicking into the wrong tab many times.

Kill me.

Doh! Lost more information again. Darn Google drive!! It would be SO nice if the backup's would record window positions, etc like a regular save does, so it's not such a pain to revert to. It's also unfortunate that this wasn't fixed in the latest version... hopefully the next as this shouldn't be a difficult fix.