Undo colouring bug

[Madman]

Hi Jesse,

This bug as been around for a while, but now it is starting to bug me...  : If you open a saved file and change the colouring, undo (for colouring) will skip back to the default colouring and not to the previous (saved) colouring. No big problem, but it would be nice if it could be fixed sometime.

[blob]

I don't think the absence of history in a saved project file counts as a bug... 

And  I don't think it's a sensible feature request either, just my 2c.

You might perhaps find what you're looking for in the M3D history folder however.

[Madman]

It is not about the history before I saved the m3i file.

Let me try to express myself a little more clearly... When you open M3D, you have a default palette (consisting of blues, greens and yellows). The next step is to open a saved file. You then get the palette from the saved file. Next, change something in the colouring. Then press the undo button. In my world, you would then go back to the previous palette. But in M3D, it skips the previous one and goes back to the default palette. I consider that a bug...

[blob]

OK so I understand now and I thought you were speaking about m3p.

[Jesse]

It is not about the history before I saved the m3i file.

Let me try to express myself a little more clearly... When you open M3D, you have a default palette (consisting of blues, greens and yellows). The next step is to open a saved file. You then get the palette from the saved file. Next, change something in the colouring. Then press the undo button. In my world, you would then go back to the previous palette. But in M3D, it skips the previous one and goes back to the default palette. I consider that a bug...

I know what you mean, the light params should be stored in history right after loading parameters...

Of course they are not really lost because they are stored, so calling a non-feature as a bug is really cruel