Hi,
 
For a couple of weeks I am having the problem; the undo description is not correct although the undo functions properly.
 
So for instance if you record something and go to menu-->undo, it displays "undo <event edit>" ( or some other arbitrary command which is not "record" but should be), but if you click it, it really undos the recording action.
 
The wrong action that is displayed in the undo description looks like a change that was completed 2 or 3 undo actions before.
 
A bug probably. 

It's been that way for a long time and been mentioned here many times, but it's clearly not important enough to be considered worth fixing. I know the square root of nothing about programming, but it used to work, so how hard can it be to rectify ? Drives me nuts that they ignore this basic fault release after release after release and spend all their time working on stuff we didn't even know we needed.

paulo
It's been that way for a long time and been mentioned here many times, but it's clearly not important enough to be considered worth fixing. I know the square root of nothing about programming, but it used to work, so how hard can it be to rectify ? Drives me nuts that they ignore this basic fault release after release after release and spend all their time working on stuff we didn't even know we needed.

I totally agree with you. I couldn't find the courage to buy this lifetime update thing because of such small bugs.

The point is, yes these bugs are not completely blocking the workflow, but they reveal some amateur software development is taking place behind the scenes.

I also fear that sonar has now grown up to such a size and extent that even the most basic functionality is breaking and because of all these agile development thing, people don't test the software properly and nobody is fixing them.

My support will end within a couple of months and by then I may consider alternatives depending on the renewal price.

I've reported this in a problem report form, in a nutshell, it works fine if all your actions are menu-based or keyboard shortcut-based but it gets screwed up if you combine them.

it seems that there have been "issues" with undo/history for quite some time now
 
the problem with "agile" development is that, while new features keep on coming, bug fixes are slower, and the end user ends up in an endless beta phase
 
it'll be interesting to see how the next 12 months pan out, the "in the oven" website section has been quite empty recently

ghanedan

paulo
It's been that way for a long time and been mentioned here many times, but it's clearly not important enough to be considered worth fixing. I know the square root of nothing about programming, but it used to work, so how hard can it be to rectify ? Drives me nuts that they ignore this basic fault release after release after release and spend all their time working on stuff we didn't even know we needed.

I totally agree with you. I couldn't find the courage to buy this lifetime update thing because of such small bugs.

It's funny that you say that because for a long time I resisted Plat based on my feeling that if they can't be bothered to fix basic things in what I have already paid for then I can't be bothered to pay again. Eventually the return of the dark UI and the "end" of the lifetime update offer sucked me in, plus I thought...surely they'll have fixed the undo thing by now...........Wrong !!
 
I'm happy to have my dark UI back, so I don't regret the purchase as such, even though it was effectively paying for something that I used to already have, but I am disappointed that they still ignore the basics in favour of shiny new things.
 
Sometimes I almost convince myself that it's a deliberate ploy for the same reason that if anyone ever produced a car that didn't wear out or break it would ultimately negate any need for anyone  to ever buy another one, but I'm sure someone will be along soon to tell me how wrong that is.