Prodoc 2004-02-03 09:56
The latest release of ultramon seems to leave more icons on the taskbar after closing an application.
The icons stay, you can click them and they do indent but nothing else happens.
Right clicking the icons doesn't display a menu.
The problems atleast occur with eMule and Adobe Reader 6.x.
Using WinXP sp1
|
Christian Studer 2004-02-04 06:46
Unfortunately I can't reproduce this issue.
For further troubleshooting, please do the following:
1) close UltraMon, then make a backup copy of RTSUltraMonHook.dll in your UltraMon directory, usually C:\Program Files\UltraMon
2) download umhook_wnt_24_dbg.zip and extract it to your UltraMon directory. This file is for Windows 2000/XP or later only
3) download DBWIN32.EXE and run it
4) start UltraMon again (shortcut under Start menu > Programs)
DBWin32 will now show lots of messages beginning with UMTbar. As soon as the problem with remaining task buttons has occurred, go to DBWin32, select File\Save from the menu and save the log to a file. Please send me the log file by e-mail to support@realtimesoft.com.
Christian Studer - www.realtimesoft.com
|
Jan 2004-03-16 17:50
The problem is happening here also. Especially when I am debugging my own application using Visual Studio .NET 2003. After an error occurs, sometimes the application remains in the smarttaskbar, while it already has been closed (the hard way).
Do you still need those logs?
Jan
|
JP 2004-03-16 17:59
Since someone else here is using Jan already, I will use JP from now on. Sorry for posting the previous message under Jan.
JP
|
Christian Studer 2004-03-16 21:19
Yes, that would be helpful.
Forcefully terminating an application shouldn't be a problem for UltraMon. What happens if you put Notepad on a monitor with an UltraMon taskbar, then terminate notepad.exe using Task Manager > Processes, End Process?
Christian Studer - www.realtimesoft.com
|
JP 2004-03-23 22:02
Not able to reproduce it at this moment. I'll leave the debug version running. As soon as I can reproduce, I will sent the logs.
JP
|
JP 2004-03-28 18:42
It took me a couple of days to refind the reproduce path, but finally here is the log:
512: UMTbar: shp wp 0x00000002 lp 0x003807E0
512: UMTbar: shp wp 0x00000002 lp 0x003807E0
512: UMTbar: shp wp 0x00000004 lp 0x0008064C
512: UMTbar: shp wp 0x00000102 lp 0x003807E0
512: UMTbar: shp wp 0x00000104 lp 0x0008064C
512: UMTbar: shp wp 0x00000004 lp 0x0008064C
512: UMTbar: shp wp 0x00000104 lp 0x0008064C
512: UMTbar: shp wp 0x00000004 lp 0x00070296
512: UMTbar: shp wp 0x00000104 lp 0x00070296
512: UMTbar: shp wp 0x00000006 lp 0x00070296
512: UMTbar: shp wp 0x00000002 lp 0x001002C2
512: UMTbar: shp wp 0x00000002 lp 0x001002C2
512: UMTbar: shp wp 0x00000001 lp 0x000F02AE
512: UMTbar: shp wp 0x00000004 lp 0x000F02AE
512: UMTbar: shp wp 0x00000104 lp 0x00000000
512: UMTbar: shp wp 0x00000002 lp 0x000F02AE
512: UMTbar: shp wp 0x00000002 lp 0x000F02AE
512: UMTbar: shp wp 0x00000004 lp 0x00070296
512: UMTbar: shp wp 0x00000001 lp 0x0018035E
512: UMTbar: shp wp 0x00000004 lp 0x0018035E
512: UMTbar: shp wp 0x00000104 lp 0x00070296
512: UMTbar: shp wp 0x00000104 lp 0x00000000
512: UMTbar: shp wp 0x00000002 lp 0x0018035E
512: UMTbar: shp wp 0x00000002 lp 0x0018035E
512: UMTbar: shp wp 0x00000004 lp 0x00070296
512: UMTbar: shp wp 0x00000006 lp 0x000F02F2
512: UMTbar: shp wp 0x00000001 lp 0x000C07BE
512: UMTbar: shp wp 0x00000004 lp 0x000C07BE
512: UMTbar: shp wp 0x00000104 lp 0x00070296
512: UMTbar: shp wp 0x00000104 lp 0x00000000
512: UMTbar: shp wp 0x00000002 lp 0x000C07BE
512: UMTbar: shp wp 0x00000002 lp 0x000C07BE
512: UMTbar: shp wp 0x00000002 lp 0x000F02F2
512: UMTbar: shp wp 0x00000004 lp 0x00070296
512: UMTbar: shp wp 0x00000006 lp 0x001302AC
512: UMTbar: shp wp 0x00000006 lp 0x001607B8
512: UMTbar: shp wp 0x00000006 lp 0x001607B8
512: UMTbar: shp wp 0x00000001 lp 0x001607B8
512: UMTbar: shp wp 0x00000004 lp 0x001607B8
512: UMTbar: shp wp 0x00000104 lp 0x00070296
512: UMTbar: shp wp 0x00000104 lp 0x00000000
512: UMTbar: shp wp 0x00000002 lp 0x002507E2
512: UMTbar: shp wp 0x00000004 lp 0x00070296
512: UMTbar: shp wp 0x00000006 lp 0x00070296
512: UMTbar: shp wp 0x00000104 lp 0x00070296
512: UMTbar: shp wp 0x00000004 lp 0x00070296
512: UMTbar: shp wp 0x00000104 lp 0x00070296
512: UMTbar: shp wp 0x0000000E lp 0x001C07A2
512: UMTbar: shp wp 0x0000000D lp 0x001607B8
512: UMTbar: shp wp 0x00000002 lp 0x001607B8
512: UMTbar: shp wp 0x00000002 lp 0x001302AC
512: UMTbar: shp wp 0x00000006 lp 0x00070296
512: UMTbar: shp wp 0x00000002 lp 0x001102BA
512: UMTbar: shp wp 0x00000002 lp 0x001102C2
512: UMTbar: shp wp 0x00000002 lp 0x000C07BE
512: UMTbar: shp wp 0x00000002 lp 0x000F02AE
512: UMTbar: shp wp 0x00000002 lp 0x0018035E
512: UMTbar: shp wp 0x00000006 lp 0x00070296
512: UMTbar: shp wp 0x00000004 lp 0x00B70658
512: UMTbar: shp wp 0x00000104 lp 0x00000000
Now I have a reproduce example also:
Conditions:
Windows XP SP1 on a Toshiba A10 laptop.
Original taskbar is running on my external monitor, identified as secondary monitor.
SmartTaskBar is running on my (internal) laptopmonitor, identiefied as the primary monitor.
1) Using Visual Studio .NET 2003 Create a new C# Windows Application.
2) Place a button on the form
3) In the button1_click event place the following code:
Form x = null;
x.Show();
4) Run the project with F5
5) Hit the button
6) Press break, when asked to break or continue
7) Press F10 for stepping one line further
Result will be that the application closes, but "Form1" is still visible in the SmartTaskBar.
Hope this helps you in solving the issue, because I like your product very much. However walking into these problems a lot, makes it less efficient.
Good luck,
JP
|
Christian Studer 2004-03-28 20:39
Thanks for the information, I have now been able to reproduce the problem.
I noticed that the Form1 button actually stays on the Windows taskbar as well (without UltraMon running), but gets removed if you either click on it or activate another application.
Should be fixed in the next release.
Christian Studer - www.realtimesoft.com
|
