Undo

[Matt]

Does anyone have any insight into why Undo works sometimes and not other times. I make a living selling my time. I use depend on PowerCADD to do this. This feature of the software is inexplicably random in it's function to me, and it's a not-insignificant problem. As much as I love PowerCADD, it is not an easy question to answer when someone wants to know if I recommend it. Flakey Undo costs me money. I'd rather give my money to a company that understands this when they write software, instead of wasting my time dealing with this.

[JohnMorse]

If you're using PowerCADD 7 there's some explanation of the Undo levels on pp. 4-68 and 4-69.

[Matt]

John -- What I am talking about is when Undo suddenly becomes unavailable. The menu item is dimmed and PowerCADD can't undo. Randomly. It happens and it's a problem. I don't know why.

[dF]

Me too - same thing not more than an hour ago (random loss of undo). Quitting and restarting the program seems to fix the problem.

[Matt]

dF --

Quitting and restarting the program does not fix the problem.

Quitting and restarting the program and REDOING what you had tried to UNDO fixes the problem.

And wastes time and concentration that should be spent on other tasks.

[dF]

I should clarify - quitting and restarting the program seems to re-engage the undo function for me anyway (v7.06)

Agree it is a re-occurring problem and happens on my G4 laptop maybe once every few weeks forcing a decision to choose between a "revert-to-saved" scenario or a "quit-and-save-changes" with everything in between vaporized either way.

[GaryV]

Matt, I agree that this is a bug that has been around way too long and should be addressed. Even ES telling us they have been able to replicate the problem (or not) and are trying to fix the problem would be a nice start.

However, as you know, they have been very inconsistent about how they use this board. When they want something like lab rats, err, I mean beta testers or want something from us so they can do their job, they post proactively. However, when we reasonably ask for something to be addressed, you can usually hear a pin drop.

So ES, any updates on the status of your investigation into this issue or is this a non-issue in your mind? I would spend 10x the time working on bugs like this than new features as, to Matt's point, the inadequacy of the program to function reliably in these cases is inexcusable. Help your users please!

Just an opinion. I am sure some will disagree.

[JohnMorse]

This board is an avenue for discussion. If what you need is technical support, try "support@engsw.com".

[Matt]

Right, but emails sent to that address are not indexed by google and available to be searched by potential customers.

[Derek]

The other good reason for using a forum to discuss bugs is that we can use snippets of information from lots of users to help diagnose the problem.

Look here to see an example: Jumping Layers

So, let's get back to the first line of Matt's post:

[GaryV]

This board has been used for many things over the years including tech support. ES says they read the board so why not discuss these things here?

I think of tech support as help with issues that are known or that the user is not doing correctly. Bang, usually fixed right away. Bugs are quite different in my mind.

There is nothing wrong with recognizing a problem and saying you are working on it. It is better than the silent treatment. And to think that maybe a user's input on this board might even help solve the problem. What a concept!