Filter bug is freakin' me out

I seem to have caught a strange bug in my DOpus 9.1.1.8 configuration. I'll set the stage...
9.1.1.7 - did not observe behaviour
9.1.18 - Started acting up only on Windows XP Pro SP3 'puter, not my Vista Ultimate SP1 'puter with same config

Whenever I try to copy or delete a file, the file filter dialog box comes up even though I have unchecked both options in the preferences dialog. I have unchecked those two options and then IMMEDIATELY chosen Save as Default Lister and backed up the config. No luck. It comes right back, but not after a particular action (at least that I've been able to figure out) or timeframe, for some weird reason. The EXACT same config on my Vista works fine, though. I have one saved filter and it is only called from a button, but it also resides on my Vista computer...
Just wondered if anyone else had had this problem or knew of a fix.
And PLEASE don't ask me if I have run a virus/spyware check or whether it is a valid copy of DOpus...I have and it is...
:slight_smile:

Check your config for any buttons which turn on the Copy filter.

The last time someone had a problem like this it turned out that one of their buttons turned on the filter and they had forgotten about it (or didn't realise it would do that).

They'd turn the filter off and everything would seem fine, then later they would run the problematic button without knowing it did anything wrong, and then the next time they did a copy the filter dialog would appear.

If you search the files in your /dopusdata/Buttons folder for "filter" using a text editor then it should make it easy to find the command, if I'm right.

Thanks, Leo. As usual, you were right. I did what you suggested and found one that had been active a long time ago. The strange thing is that it wasn't being used by any button that was active anymore...It would make sense to me if the button was still being called (on one of my active toolbars) but it wasn't...starnge. Anyways, problem fixed... thanks!

A User Command? Something must've been calling it; maybe the file display double-click event was set to do so?