"WBT- " Prefix on Taskbar

[MrLeadFoot]

I've noticed that some, not all, of my compiled scripts show a pre-pended "WBT-" on the taskbar. What causes this, and how do I get rid of it?

To be clear, some show the title of my script normally, but some show "WBT-" then the title.

I've compared the .CMP files of ones that do and ones that do NOT show this prefix and don't see anything different, settings-wise.

Thank you.

[JTaylor]

A couple of things to check.   You can use WinTitle() to fix that in some cases.  If you have a dialog interface and two icons show in the status bar you can use WinHide("") to hide the window so only the dialog icon shows or use WinTitle() and keep both.  It, of course, uses the title in the dialog settings.

Jim

[MrLeadFoot]

Thank you for the reply, Jim.

I don't have two icons in the taskbar, so when I try WinHide(""), it supresses the script icon.

When I use WinTitle("",[My Text]), this works ONLY if the compiler's Run script hidden checkbox is unchecked, but if I click on the icon in the taskbar, I get the script's interface with the interpreter window behind the script.

If checked, I get no icon in the taskbar, even if I have a dialog interface. My other similar scripts that don't have the "WBT-" problem, show an icon with the proper name when an interface dialog is displayed even though Run script hidden was checked during their compiling, so I don't know why these other scripts are having this problem.

Any other suggestions?

[JTaylor]

Understood on first point.  You would only see two if you had a dialog, at least that has been my experience.

#2.  That makes sense.  If you hide the script one wouldn't expect to see it.  background window is expected behavior when you click on icon.  A bit annoying at times.   I would think if you hide the script, the title should still change with WinTitle.  Obviously you wouldn't see it but TaskManager should reflect the correct title.

If you post an example with this problem and outline the settings you use and what you expect to see as opposed to what you are seeing, I am happy to try it here.

Jim

[MrLeadFoot]

Understood on first point.  You would only see two if you had a dialog, at least that has been my experience.

#2.  That makes sense.  If you hide the script one wouldn't expect to see it.  background window is expected behavior when you click on icon.  A bit annoying at times.  I would think if you hide the script, the title should still change with WinTitle.  Obviously you wouldn't see it but TaskManager should reflect the correct title.

If you post an example with this problem and outline the settings you use and what you expect to see as opposed to what you are seeing, I am happy to try it here.

Jim

Sorry it took so long to reply. I had a heart attack that took me out for a while. Hopefully it wasn't this issue that caused it! Nevertheless, I JUST figured out this weird behavior:

Scenario 1 - Script does NOT contain a WIL Dialog, and instead uses Pause or Message dialogs

a) If you compile the script as "hidden", you get no taskbar icon at any time, even when a Pause or Message is displayed.

b) If you compile the script as NOT "hidden", you get a taskbar icon, but its name prepended with "WBT- ". As you mentioned, you can use:

Code Select Expand

WinTitle()

...to get rid of the prepended "WBT - ", but if you click on the taskbar icon, the WIL Interpreter window pops up behind the script window.

Scenario 2 - Script contains a WIL Dialog

a) If you compile the script as "hidden", you get no taskbar icon at any time, even when the WIL Dialog is displayed.

However, if you include the following line in the script:

Code Select Expand

IntControl (49, 3, 1111, 0, 0)

... when the WIL Dialog is displayed, you get a taskbar icon with the correct title NOT prepended with "WBT - ", even if you don't minimize the WIL Dialog.

b) If you compile as NOT "hidden", you get the WIL Dialog icon AND a WIL Interpreter icon.

Now that I know these idiosyncracies of the Compiler, I will stick with Scenario 2a in the future, but I'm curious - why is there a WIL Interpreter window to begin with? Does it serve a purpose (other than rename titles and cause confusion) that's useful and I am just not aware of?

[JTaylor]

Maybe that is why I never had the issue as I usually/always(?) make use of IntControl 49???

Sounds like you have it mostly sorted out.

Last question seems like a Tony question to me so I will bow out.


Jim