something shouldn't really be a reason to change how that thing works - there is even scope for infinite regress here, if someone forgets to save a file (a really really basic part of using software)

Are you looking for a specific way to calculate/display it other then whats been laid out? Like highest clicks per second achieved vs actively updating clicks per second?

I've merged these threads. Please don't start a new thread for the same issue.

Yes, pretty much.

more useful, you could use it to lay out dotted lines, dashed lines, patterns of all sorts, but with the production of particles being random it prevents the behaviour from being used in so many more

I would round the value seconds and clicks per second, but perhaps you need a exact value.

I guess I wasn't asking for the righ thing in my other discussion, but how would I make a clicks per second calculator like in Cookie Clicker?

I avoid the particle behaviour pretty much entirely. The benefits of spawning your own particles are:

I'd imagine that if there is such a thing as a "standard" of doing things it would be:

When you want to have a running copy of a project and the option to fall back to older versions you need a versioning system - like GIT, SVN, ...

You can, you just have to use numeric expression rather than text expression when checking the table value. This will still work even when the bug is fixed, so you can make the changes now without iss

Is it only the preview when mousing over that is wrong, or is the expression inside the editor when you reopen it also showing as wrong?

I'll make changes to a project, saving every 5-10 mins. If I'm going to preview a project, I'll either save it or not depending on what changes I've made. For small changes "progression&q

You've got to have a lot of spare time on your hands for this to be your standard workflow process...

test, and pick rules apart, but you'd have to be much more cautious about what you are doing, you'd always need to do some extra preparation and/or a Save As before starting to play around with code

Let me just clarify something here: is your standard workflow is to make a change, preview, and if you're not happy with it, reload the file to the last version? Or do you typically just try another c

What version of the JDK do you have? Try upgrading to the latest one (8).

The Expression editor is quite not working as it was suppose to be. If you see the image i put attribute "game.Display Size.Width" but when i click check it changed to "game

It is really not that hard to save yourself and if you do not save as a new version then be prepared to redo all work since you last did when project corruption occurs. Or try to fix your corrupted pr

One reason being that a project can become corrupted and if that happens on your "only" project that has been saved over and over, how happy do you think you would be then?