Undo "bug" in Elements 13

I can't undo the first thing I do in Elements 13.
What this means is that I open a file, draw a line with the brush tool, try to undo and I can't. (I've tried esc, ctrl +Z, there's no undo icon in the task bar, and there's no Undo under Edit in the menu bar) I can undo the second and subsequent action (not a PS action, but something that you do to the image); the undo icon works.
The only way I can see to get back to the original image is to click on the file name in the History panel or use Edit > Revert from the menu bar. This is a pain in the patootie. Is this a bug or a new "feature" Anyone else have this problem?
Tried brush tool, clone stamp, shape tool, etc.
Details:
PSE 13 on Windows 7, expert mode.

there's no Undo under Edit in the menu bar
Something is very wrong if you're in Expert mode:

Similar Messages

Undo bug, mouse pointer disappears?

Is just me or everyone has that annoying "undo" bug?
That's what happens: when I press UNDO speedgrade starts to behave strangely.
- If I press undo after clicking right mouse button (and I'm moving a color wheel with mouse) comes out a message "optimizing timeline" and timeline thumbnails are shown under the timeline. Sometimes there is a worst scenario: mouse pointer disappears and I have to quit SG and reopen to get my pointer back.
- Pressing ctrl-z without right mouse button clicked (outside wheel edit mode, or whatever it is called..) sometimes works, sometimes appears the annoying progress bar "optimizing timeline" and several steps of undo are taken, even if I pressed cmd+z just one time.
I use undo A LOT, and now I'm not confident using it because of this strange behavior (I'm on osx).
Are you experiencing the same problems?

You won't believe this but just cleaning a mouse can improve performance... read the following:
How to Clean a Mechanical Mouse
This article explains when and how you should clean a mechanical mouse. It does not apply to the the Apple Pro Mouse.
You should clean a mouse if it is does not track smoothly, or if it jumps or skips. A mouse contains a small ball that must roll smoothly for the mouse to work properly. You should keep this ball free of dirt and oil by using the mouse on a clean, lint-free surface, and cleaning it occasionally.
Use the following procedure to clean a mouse:
1. Turn off your computer.
2. Turn the mouse upside down and rotate the plastic ring on the bottom counterclockwise to release it.
3. Turn the mouse right side up with one hand and catch the ring and ball with your other hand.
4. Clean the three small rollers inside the mouse with a cotton swab moistened with water. Rotate the rollers to clean all around them. If there is a build-up of material on the rollers that the cotton swab does not remove, you can use your fingernail to gently remove the material.
5. Wash the mouse ball in soapy, warm water with a mild soap such as a dishwashing liquid if oil from your hands has collected on it. Be sure to dry the mouse ball thoroughly.
6. Gently blow into the mouse case to remove any accumulated dust.
7. Put the mouse ball back in the mouse case and replace the retaining ring.
If cleaning the mouse as described does not correct your issue, the mouse may need to be replaced. Have an Apple Authorized Service Provider check it for excessive wear or other failure.
If that doesn't do the trick, if this is a mouse that required 3rd party drivers, you might try reinstalling the drivers. Also, try going back to default Mouse preferences on all Users, see if makes a difference.
Carolyn

Are there still bugs in Elements 4

Are there still bugs in Elements 4?
Looking at the feature list I am tempted to buy Elements 4. But I have read many reviews that indicate that it is "bug ridden"- most reviews are dated just after release. Have Adobe fixed the bugs now?
Advice very welcome...

Unfortunately you seem to be suffering from what has come to be known in PE4 terms as the "Goldilocks Syndrome". Do you remember when Goldilocks ate the porridge; one was too hot; one was too cold and one was just right. This went on with the beds etc. Well, it seems (from this very forum) that PE4 has a similar problem; if your computer is over specified (even with ALL the latest available drivers installed), it won't run properly; if it is under specified (even with ALL the latest available drivers installed), it also won't run properly, it has to be just right. There are people out there who's computers are just right, as we don't hear from them, obviously.
See if you can take your copy of PE4 back to the shop (they should have told you that a new one was coming out, well, if they were a good shop) and wait for PE7 which should have all the PE4 bugs worked out. They don't have to do much with the interface as it's already flawless. Very difficult to improve on the best. They just have to make sure it works on E-V-E-R-Y-O-N-E's computer.
Have a look at Steve's PE7 introduction video's on the Adobe website. That's how a software should work.
Best of luck.

FURIOUS! Warning: Undo Bug and Auto-Save Bug

So I'm pretty ticked off right now. I generally liked FCPX and its changes contrary to many others' opinions, but I just came across a bug that ultimately was worse than I thought.
During my editing process, at some point I was unable to undo changes. It was greyed out in the toolbar, and Command+Z wasn't working. It was annoying, but I didn't think much of it or bother to restart FCPX because I was in the zone and didn't want to stop. Eventually, I decided to restart FCPX to see if I could fix the bug with a lull in my edits. It closed out as normal.
When I re-opened FCPX, I found out that my project was at an EARLIER state. From what I can guess, when the undo bug happened. So, during that period of time, NOTHING was being saved. Since you CANNOT auto-save (I know you can duplicate a project, but Im not interested in that, I just want to save a copy manually), there is no way I can recover my edits. I lost about an hour or so worth of edits. Since FCPX doesn't support "versions" yet either, there is no way I can retrieve it.
I do not know if this is a bug due to 10.7, nor do I really care. I sent a bug report because this needs to get fixed. I consider you do the same but AT THE VERY LEAST, be mindful of this bug. If you suddenly can't start undoing, either STOP IMMEDIATELY or duplicate your project (maybe that would work). I'd hate to have someone else go through this problem too.
Sorry if this message is written poorly, like I said, I'm pretty ****** that this key function (Apple's ONLY way to save) failed.

Thanks guys for the tips. Unfortunately though stuck, I don't know if the finder trick will work. Remember, I never really had the file LOST, the changes were simply not writing to the actual .fcp file. So if I copied it in Finder, I think it would just copy the .fcp file which is currently not getting saved to anyway. Maybe duplicating the project in FCPX would work, but again I think that just takes the .fcp file and duplicates it. If it's not writing to it, then its a moot point. Oh well.
As with anything that frustrates anyone, I've cooled off haha, and doing the re-edits actually seemed to turn out easier and better then second time (you know, as theu naturally are I suppose haha). Obviously all sorts of problems happen with technology, its just a shame that its a bug that revolves around the ONLY save feature haha.
HOWEVER. I think I have replicated the problem, and MIGHT know the source of it. Or at least one. If someone wants to try this and confirm this? I'm running OSX 10.7 and FCPX 10.0 (obviously), however I encourage someone with 10.6 to try it too.
I noticed the "undo bug" (and thus the auto-save bug) happens when I took one of the "fader handles" (I don't know the actual name, but its the little marker-like icon found at the start and end of audio tracks, which when dragged, let you easily make a fade in or out. If you take a fader-handle, an drag it ALL the way BEYOND the length of the clip, it should get stuck. Youll notice you cant easily make a change to it again, and you can't undo it. I think this is what causes the problem, as I think this happened twice to me.
If this is it, I hope I can find a way to flag this for Apple so it can get fixed! At the very least we can be concious of it.

How much longer will we have to wait before Adobe fixes the bugs in Elements 10?

Lassoo misbehaving - I use it all the time - I'm seriously thinking of consigning Elements 10 to the bin and going back to Elements 8. Can't save file owing to program error - every second or third save - drives me bananas. I know, I know, if I click in the corner of the box a couple of times it works again but I expect a program to work as described not to have to patch it up myself.
So come on Adobe pull your finger out and fix it - I spent my money on your product now you spend some of yours on getting it right.

If you look around at all the forums and support sites you will find this exact same question be asked everywhere concerning numerous bugs. Right now the only answer you get is "try elements 11 you'll like it". So in my humble opinion I think ADOBE plans on fixing the bugs in elements 9 and 10 when you know what freezes over and not a minute sooner. For all those considering elements 11 you might want to wait and see what shows up in the forums concerning any bugs it may have, because based on any past experience they won't fix until next version (12) comes out, in other words you become the beta tester for the next version.

File menu bug in Elements 8 for Mac

I recently purchased Photoshop Elements 8 for Mac. While the software overall works very well, I noticed a bug which has now started hampering my work. Out of the blue, 'Open', 'Open New Blank File' and 'Browse with Bridge' in the file menu become grey (disabled) and shotrcuts for opening files (Command-O and Command-N) or clicking on the open new file icon yield no result. Preferences menu cannot be accessed as well. As per the software license, I installed Elements on an iMac running OS 10.5.8 and on my MacBook running OS 10.4.11 I am having this problem on both :-( The menus do appear but intermittently. Any help to fix this bug would be deeply appreciated. Thanks in advance.

I got it!!!!!
It's a clipboard related problem! Whenever I copy an image (a vector image or graphic specifically) from any application, New 'Image from Clipboard' option (in the file menu) gets enabled in Elements 8 and due to it, all menus relating to opening a new file get disabled including, strangely, preferences. Somehow Elements assumes that the new file/image will be the same as the one in the clipboard. The moment I copy any text in any application (so that the clipboard does not have any graphic in it), the disabled Elements menus get enabled! It seems Elements 8 does not support vector graphics perhaps that's why..

Bug in Elements 12 with Thumbnails.

Under PSE-10 I had an occassional bug with thumbnails in that sometimes they disappeared and were replaced with grey squares. Right-clicking "Update Thumbnail" got them back, even if sometimes not for long.
I had hoped that in PSE-12 the bug would have been fixed, but in fact it is much worse. PSE-12 gets into a state where if I scroll through my pictures (about 18'000) some of the thumbnails first appear and then very quickly they are overwritten in grey. Sometimes Update brings them back, but often it doesn't. Sometimes changing the magnification gets the images back, and sometimes it doesn't. Moreover, changing the magnification seems often simply to rescale an image by pixel replication without recalculating from scratch, leaving a badly out of focus image.
Has anyone else seen this effect and, if they have, found a remedy? (Well, it is not impossible, I suppose...)
David M.
(I am using Windows 7 with all updates on a 6 GB machine with a 30 inch 2560x1600 screen)

D-R-M a écrit:
I spoke too soon. After a short amount of playing with PSE-Organizer the thumb.5.cache file is back up to 663 MB and the thumbnails are quickly being replaced by grey boxes with a broken link icon.
I was going to tell you that 35.6 MB can't hold all your thumbnails. 663 MB seems the right size.
About files the thumbnails of which don't update : are they very big files ? are they raw files ?
Here is an old Adobe paper about similar symptoms in PSE6:
http://kb2.adobe.com/cps/403/kb403728.html
It may be time to delete the organizer preferences and status:
"C:\Users\[your name]\AppData\Roaming\Adobe\Elements Organizer\12.0\Organizer\psa.prf"

Is it a bug about element's depth?

I have two elements in one frame and if I use:
alert(fl.getDocumentDOM().getTimeline().layers[1].frames[2].elements[0].depth);
alert(fl.getDocumentDOM().getTimeline().layers[1].frames[2].elements[1].depth);
It shows me 0 and 1, It is all right!
But if I don't select two of them , the depth is 2 and 2!
How it possible!!!!!
Is it a bug?

Hi,
It works correctly for me. Can you share your test file along with the steps so that we can have a look at what's going wrong for you?
Please note that simple shapes(unselected) at the same layer have the same depth. If you have a drawing object or a symbol instead, then their deapth would be different.
-Nipun

Odd Camera Profile / Undo Bug in 2.3 RC

I downloaded the LR 2.3RC tonight and although it seems to be running faster, I've noticed a strange bug that I've never noticed before (or that wasn't there before.
When using develop presets that change the camera profile (for example Matt Kloskowski's 300 Look) the preset will be applied and then after that the camera profile is changed as a separate step in the History palette (however I have only clicked on the preset and haven't changed the camera profile).
When clicking undo the overlay that tells me what step I am undoing says that it is "Undo Camera Profile: ACR 4.4" - however this step either (1) gets undone and immediately re-applied, or (2) never gets undone. This problem makes it impossible (without using the History palette) to revert to the step before - and it kind of makes it difficult to apply several presets to see which works best as I have to scroll to the History palette to undo it and apply another.
This bug only exhibits itself when using presets which change the camera profile.
Anyone else seeing this?
Any work arounds (other than reverting to 2.2)?
Thanks,
Chris

Hey Chris,
Yes I can reproduce this same exact problem on my Macbook Pro (Feb. 2008) with 4GB RAM and 10.5.6 with Lightroom 2.3RC
I tried this on Lightroom 2.2 and I can say that this problem does not happen. This is a Lightroom 2.3RC bug.
Is there a place where we are suppose to report RC bugs or is this post enough? Thoughts Adobe?

Reporting a bug in Elements 13 to Adobe

Can someone please let Adobe know about the bug in software Elements13. People cannot print , default printer will not open, using "Editor". Read the messages in "Forum", many people have the same problem. I spoke to Adobe on phone, but they were not interested in what I told them. I also have problems with the sizing when trying to add a border. Does not go/remain to correct size that is entered. Tested with using same printer sizing the borders on four other versions of Elements & Paintshop pro x7. No problems with printing or sizing borders. This bug needs to be fix by Adobe, sooner , rather than later, for the sake of all who have Elements 13.
Thank You

Please update PSE 13 to PSE13.1 using Help > Updates and see if it helps.
Thanks,
Anwesha

LR4 adjustment brush undo bug

Think I have found a bug in the LR4 beta, it's reproducible by me anyway.
Paint an adjustment of any type onto an image using the adjustment brush.
Now select the erase brush and erase part of the adjustment you have just made.
Click undo.
The undo is made, but the erase brush also changes back to the add brush (Brush B in my case)
I have found myself finely erasing adjustments, and then accidentally adding them again after clicking an undo.
Can alone else confirm?
LR4 beta, Windows 7 64bit.

The place you should be posting to is the Lightroom 4 Beta Forum...

Undo Bug

Lightroom 5. I'm running througn shots for technical checks. I want to keep one file and reject 2 others so I mark them as such, that is in my workflow I change the red label (Waiting For Selection) to green (Selected) and the other 2 to yellow(Rejects).
Except that I have inadvertently left all 3 files selected (highlighted) so when I change the label on the 1 meant to Selected (green label), in fact all 3 are labelled green. No problem, ctrl Z or Undo Toggle Selected Label' on the menu will bring them back.....
Except it doesn't. What it does is change the next 2 files in my run through shots to B/W. The Toggled files stay where they are, the labelling is not toggled. I can put the colour back in my files by going to Develop module, Basic / Treatment where they appear as 'Black and White' and clicking on Color.
I hope this makes sense. Anyone care to try to reproduce it?
To simplify:
Make a Collection of (say) 20 files labelled Red
Make an empty collection of files labelled Green
Right click on 3 Red labelled files
Those files now disappear from the Red Collection and appear in the Green Collection.
Now go to Edit->Undo Toggle Green Label
The green labelled files stay in the Green label Collection
But a couple of files in the Red Collection convert to Black and White.

No interest? I'd just like to know if this is an oddity on my system or is general. In which case I'd repoort it.

Photoshop CC undo bug with shapes

I'm wondering if anyone else has experienced this problem. I'm using Photoshop CC on a PC and when I change the color of a shape if I ctrl+z to undo, it often (but not always) gives me this message the first time
and then crashes if I try to ctrl+z again giving me this error
For the most part I've gotten pretty good at remembering never to try and undo a shape color but sometimes your fingers hit those keys so quick that it gets annoying to have the goofy program crashing on you.
One thing to note is it works fine when you first make the shape, I can undo/redo no problem. It's when I go back to edit a shape that this problem occurs.

Hi,
Glad you were able to get the update. That is a Win only issue in 15.0.0 that we fixed and updated in 15.1.0.
regards,
steve

Photoshop CC selective color UNDO BUG

do this in photoshop CC:
- open an image
- layer -> new adj layer -> selective color
preset: custom
colors: reds
cyan -100%
press ctrl+z for UNDO
it restores the effect on the image but it doesnt update the setting to 0%
same thing in all adjustment layers, exposure, levels, curves..
this sucks!
doesn't work even through history tab
my hardware?
core2duo 3.16
6gb ddr2 1066
nvidia 9600gt with the latest drivers
ssd
windows7 64bit
any ideas?

i had this issue too.
press CTRL + K
or go to edit -> prefrences -> general
go to performance section
and press the DEFAULT button
and assign a scratch disk (c:) for example
press ok
restart photoshop and you're done probably
well that worked for me though.

Bug: Null Element Width and Max Width on page item won't stay null (v3.0.1)

Well, it's pretty much what it says. I'm trying to edit a page item and remove the width and max width on the Element properties. When I remove them and hit apply it functions properly, and the page item shows up with no width or max width property set. However, if I go to edit the page item again, the Width and Max Width fields are populated (30 and 2000 respectively) again. Thus, any action which saves the item will save the unwanted values. I don't want a width and a max width on the item; it shouldn't put them back.

I think default values should only be used in a
situation where no value has previously been
provided.
How can I tell the difference between the case where
I fetch a null value from the column because a null
value was previously saved and the case where "no
value has previously been provided"?Well, I would assume that there is something unique about the initial creation of an item versus the editing thereof (e.g. the item does not exist in the database, yet). It's only on create that you would want to provide default values, that is, when no value has previously been provided by the user. Any other time the item is edited, it already exists and any values submitted should not be overridden or replaced. Off the top of my head, this could be done with table level defaults (if all item types were to share the same defaults for all properties), or via an insert trigger. Either way, the defaults would only be applied on create, and not on edit.
Message was edited by:
CaptSimian

Undo "bug" in Elements 13

Similar Messages

Maybe you are looking for