So, yeah, you get the idea. I figured it would be helpful in this area because there are a lot of stupid small questions to be answered for computers and dedicating thread after thread to just one stupid question isn't very useful. Anyways, my stupid question is actually apparently fixed now... but it freaked me out and I have no idea what happened.

Alright, so here it is. I was posting in Forum Games and suddenly every time I tried to make an apostrophe, it opened my quick find toolbar. Now it's not doing it anymore. I use Firefox, as all of you know, and I wasn't using cooliris at the time but am using it now (which I'm going to experiment with the obvious implications there in just a sec.). So, in question form, What the hell was that!?!?

Text box wasn't in focus? I dunno.

I've had that happen with different keys. Usually I just hit Esc and it fixes it.

Oooh I think I had that happen once. It was in a password input box. It kept bringing up the search. Could never figure out why. I restarted FF and it went away and hasn't done it since. Odd thing.

It's a shortcut for the find tool, if you don't have a form field in focus.

I had it in focus though. I know I did because I thought that was the problem and checked 3 or 4 times. Eh, well maybe it somehow thought it wasn't in focus or something, I don't know.

I think it's an issue with Firefox thinking the Ctrl key is being held down.

But ctrl doesn't do that shortcut. I thought that too, but I tested it and that's a no too.

It's a bug. I had the same thing happen to me. My initial thought was that I had a key stuck down, so I smashed and banged on a few keys but no luck. I had to actually restart FF for it to go back to normal.

Why?

Because it's Photoshop. I get that all the time, but usually I just try again and it works the 2nd time. I also get an error quite often that says something along the lines of "Cannot complete because you do not have enough free memory (RAM).", which is BS because I have 2GB total on my work box and it does that when there is over a gig free usually.

Still havn't figured out why. Anyone know?

Bad thing about that error is that I can't save anything after it errors, and I have to restart PS to get it to work again. Thus loosing anything that may have been unsaved.

Posted Wed Dec 13, 2006 6:23 pm:

Ah Hah! I just got your error just now. I remember why it does it (for me anyway). It has something to do with actions and the image DPI, and possibly part of the action chaning the mode.

I have an action that whenever it is run usually has the image at 600DPI. At any other DIP it throws that error. It throws it on the last piece of the action which is Convert Mode -> Bitmap.

My action is Flatten. Convert Mode Greyscale. Auto Levels. Invert selection. Auto Levels. Convert Mode Bitmap.

That help any?

Posted Wed Dec 13, 2006 6:25 pm:

Update: Looking into the details of the actions shows that the last step of convert to bitmap is trying to do specifically 600 DPI, which would make sense it would error if the image is any other DPI.

So something to do with an action converting to bitmap from greyscale with an image that has a DPI that doesn't match the action's DPI.

That confusing enough?

Posted Wed Dec 13, 2006 6:27 pm:

Ok scratch all that. It just did it again. This time no action, just converting from GS to BM, and the DPI was different. Heh. Sorry for all the crap.

As for the Firefox question -- yes, it's just a bug. I haven't seen a fix for it yet. Maybe it's possible to change the key binding in about:config?

Now, if only I knew how to do that. :p Alright, well, here's the thing though, it happened again yesterday, and it was doing it on explorer also. I ultimately had to restart my computer to fix it.

I took a quick look through the about:config and didn't see anything that looked like it would accomplish that (if you're curious, put: about:config in your address bar -- careful! Easy way to break stuff if you go changing settings in there).

After a bit of searching, I've found this: http://kb.mozillazine.org/Find_bar_open ... in_textbox

One of my results also said something about an extension for changing such hotkeys, but it was on a forum, and the post had been moved -- I was unable to locate it (see: where the crap is my [cached] link on google?).

Give that a try, though, and see if it makes a difference.

I think it was generally the multiple windows bug so that helped alot. Although, I'm still wondering what happened when it started effecting Explorer and Firefox, but that has only happened once so far, so I'm not too worried about that one.