Taskbar not popping up context menu Thread last updated on 2003-07-27 02:39:10

Posted by member 43980 on 2003-07-20 14:15:09

Hi

I'm having problems with the taskbar module in LiteStep. I've tried different themes and different versions of Taskbar3.dll, LiteStep .24.6, the latest stable of IndieStep and the problem is the same. After LiteStep starts up, the taskbar is displaying correctly and everything, but when I right-click on a task, the context menu comes up and freezes. Afterwards, I right-clicking the tasks does nothing and left-clicking on the taskbar doesn't bring up the window on top. I'm thinking it might conflicting with another module or configuration but I can't figure out which...

Thanks in advance.
-lavamind

Posted by member 39 on 2003-07-20 15:21:02 link

What's your OS? I'm running Win2000, Litestep 0.24.7 beta 3 and none of the taskbar3 versions i tried here showed that problem...

Posted by member 43980 on 2003-07-20 15:56:51 link

Windows 2000 as well... Where can I get 0.24.7?? It's the only version I didn't try yet.

Posted by member 43980 on 2003-07-21 01:12:21 link

Ok, I tried with 0.24.7 beta 3 but it still does the same thing!! I am noticing its doing this with many themes, some of them not using taskbar3.dll. Also, if I restart LiteStep.exe, the context menu functions correctly, but it doesnt fix the task button weirdness (ie when I click on a window it comes up, but goes away as soon as I release the mouse button...) I also tried incorporating the .ontop, .select etc taskbar3 settings in step.rc...

Anyone have an idea??

Posted by member 1783 on 2003-07-21 02:46:35 link

i had a similar problem, but .305 fixed that.

Posted by member 43980 on 2003-07-21 09:40:02 link

I've tried .305 and .306 beta 2 ... same thing!!

Posted by member 43980 on 2003-07-21 10:16:06 link

FIXED!!

LiteStep 0.24.7b3 + Tasbar3.dll .306b2

The taskbar weirdness was also caused by the installer not creating the DestopProcess DWORD (1). So when I opened up Explorer to check the taskbar behavior, that window would always come on top. The installer should really include this setting!!

Posted by member 7223 on 2003-07-22 08:29:40 link

ctfmon.exe, a f***king prog installed everytime you run an MS-Office XP app could cause bugs like this

Posted by member 265 on 2003-07-27 02:39:10 link

that's odd, the installer has always included the following setting:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer
"DesktopProcess"=1