Post by DarK » 17.08.2006 23:12:58
I figured out how to fix this:
Create a rule where
Window Class is CursorXP
Copy to all Desktops
Set the rule to apply automatically. f1x0r3d.
CursorXP actually creates a small window, you can see a little square on the Preview. The window doesnt have a title, but it has a class name!
In case the devs are wondering, i'm running WinXP SP2, Dexpot 1.4, CursorXP 1.31, and Logitech mouseware 9.80. I wonder if the mouse driver has something to do with it... might explain why some people didnt experience the problem.
I experienced the exact same issues the first poster had. Mouse only on the 1st desktop on startup. Cycling cursorXP off and on would add it to that particular desktop for the rest of that session (until dexpot closed). Needed to go to every desktop and cycle cursorxp every time it started, kind of annoying.
I figured out how to fix this:
Create a rule where
Window Class is CursorXP
Copy to all Desktops
Set the rule to apply automatically. f1x0r3d. :cool:
CursorXP actually creates a small window, you can see a little square on the Preview. The window doesnt have a title, but it has a class name!
In case the devs are wondering, i'm running WinXP SP2, Dexpot 1.4, CursorXP 1.31, and Logitech mouseware 9.80. I wonder if the mouse driver has something to do with it... might explain why some people didnt experience the problem.
I experienced the exact same issues the first poster had. Mouse only on the 1st desktop on startup. Cycling cursorXP off and on would add it to that particular desktop for the rest of that session (until dexpot closed). Needed to go to every desktop and cycle cursorxp every time it started, kind of annoying.