P: Photoshop creates a gude log while working with files

You say:

"1) I can open an image file with a single double-click. Now, I need two. Adobe PS is rife with inefficiencies, and it sucks having to put up with one more."

Is this a joke? You've been innefficeintly double-clicking, now I've given you a solution that uses two single clicks. Two clicks either way, not that it matters, because any editing takes dozens of clicks.

You are complaining about an "inefficiency" that does not exist. Please, enjoy yourself, do as you like and complain to Adobe not to me.

1. You double-click files? But you complained about clicks? Then why don't you change to single click to open? You must admit, that is ironic! You've been using double the clicks for how long?

2. If you have "thousands of images" and you are not using Bridge, you are in for a fantastic pleasant surprise when you do start using it.

3. If you actually read my solution post, you would not infer you have to open Photoshop first, because you don't.

Rob Ainscough - The proof of our skill sets with respect to this issue is in our comparitive communications.

1. You missed that I gave a complete solution for opening files via not just within Adobe apps but via Windows Explorer, so your criticism in that regard fails.

2. I never said it's not a bug, another fail. Nor does it matter if it is a bug, because best practices avoid it completely. [Abuse removed]

3. As for you interest in some official response from the manufacturer on this trivial issue, you may not have looked at the dates of the first complaints. Good luck, stick to your guns, click on files and then delete the log files, do not follow my advice!

P.S. I post carefully written replies here for willing learners.

@Beachcolonist ... your post is the most obserd post I've ever seen on the internet.  I wonder how you are employed to be honest?  Calling users you don't even know not professional because of a bug introduced by Adobe?

I'm a software engineer (35+ years in the professional arena both public facing and internal), this is clearly a BUG, the problem didn't exist in earlier versions and now it does exist.  Any reasonable software engineer would clearly understand this is a bug given the context of the information provided in the file ... that's debug information intended for software engineers not for end users. 

Let me ask you this, since you claim to be a professional, do you know what this error message means?

"SqliteResumeCache::CreateSqliteResumeCache creating resume cache pointer failure"

I have a pretty good idea at what the Adobe coding problem is, they're trying to reference cached data that no longer exists. 

This is 100% coding error with blame squarely on Adobe engineers and most importantly on Adobe Quality Assurance group (if they have one as it seems they don't given the proliferation of users having this problem).

But I'm certainly not going to call you or anyone else "not professional" because they don't understand programmer code references.  Only someone very insecure about themselves would defer a real bug as not being a professional user.

A solution is when Adobe address this obvious BUG.

A work around is when you inform users to only open Adobe files from within Adobe applications ... BTW, this problem is impacting Illustrator and a slew of other Adobe applications, not just Photoshop.

If you want to provide work around, great, but to degrade users as not being professional isn't relevant nor a good way to communication, share, and help.

I agree one can get around the issue of creating gude log files by doing some extra work. However, the main point is that Photoshop does not behave the way a typical Windows program should. For every other program I use, there is no difference between opening a file by double-clicking and by opening the application first. To have to purposely remind myself and make an exception for Photoshop every time I want to use a PSD file doesn't make sense. It may be just one or two extra clicks plus locating the correct app on a menu, but when you have thousands of images, it becomes significant.

Perhaps you are new to Photoshop, or new to making demands of Adobe. If so I can help:

1. It's one more click, and zero more "actions." If you think Photoshop is "broken" because you discovered it creates a file, the purpose of which you don't even know, you most likely are an edgy novice. I say this with due respect, simply because I was once a novice myself and did some complaining here.

2. If you use Photoshop via Bridge like you are supposed to for best efficiency, it's not a problem at all, it's nothing.

3. You can beat your head against a wall here making demands. They don't hurry up because of complaints about issues that professionals do not care about. I have seen Adobe just go and cancel a whole software (for website creation) and thousands of users were screwed. They complained, it did nothing.

3. Resourceful pros take great solutions like this and use them. You may reflect and realize this yourself.

There is some confusion, I'm happy to clarify.

1. If you use any one of my three (3) solutions, you will not generate a gude*.log file. In fact I edit dozens of files a day for months, and I never saw them, because I never directly click on a file. Directly clicking on a file is, with all due respect, a procedure for novices. So don't do it!

2. Ok so I did generate "gude*.log,"  and like you I wondered if there were more, and I just used Windows search for the whole SSD, searching for "gude*.log," (no quotations and no comma). The asterik is essential, because each file has it's own date, thus * acts like a wildcard. You will see every one on the drive, and can delete them all at once.

3. End of issue, as long as you take my advice about opening files in the future!

PS I can be wrong just like anyone, but I think I have this one right.

Ty for the Conclusion,

but is still annoying to have this gude.log and if you forget to delete the gude.log 

the file gonna stack in other folder and will be many gude log if you open directly your file.

Adobe Need fix this gude.log Problem