DXPro - TaskBar & SysTray dont work

Also, how to properly exit a gadget?

OK, so I created a Gadget w/ DXPro 3.1

There is an "X" exit button on my app. I set it to an object controller, it sends a Destory message to the group.

This works fine. I had someone install the app on their machine (WinXP - no stardock apps). The application itself works fine. However, they click on the Exit button and the app goes away. BUT if you look in taskmanager you still see the .exe app running in your list of processes. Not good.

So I thought, I'll recompile it and set that one option to Task Bar rather than my normal None (I know that SysTray doesn't work and exhibits this behavior, but I had not previously tried with Task Bar).

OK, so my victim, err guinea pig, err friend runs the new .exe Everything seems to work fine. He clicks on the X button to exit the app. The Gadget is still showing in the Task Bar. Right-click, close, and it's gone.

That all seems fine (well, it's still a bug w/ the zombie process left over...). Now he attempts to run the .exe again. THis time the app does not appear on the desktop. All we see is the app in the Task Bar. Click on the task bar and nothing happens (well there is an animated "flash" going from the task bar to the upper lefthand corner of the screen, but other than that nothing happens). We can't get the app to appear on the desktop so that we can actually use it. Right-click and select "Restore" Still nothing.

Basically, now after the first run, we cannot use the app AT ALL. We close it, I recompile w/o the Task Bar stuff set, and we are back to exiting the app and then having to go into Task Manager and killing the zombie process by hand. It sucks, makes it look bad, but at least it works and we can actually use the app.

This has been here since at least 3.0 (the first version of DXPro that I had.

I don't see anything anywhere about a new release of DXPro, or anything about a fix or workaround or anything, so what gives?

Thanks,

Brain21
5,346 views 7 replies
Reply #1 Top
How are you closing the widget? By script or widget controller object?
Reply #2 Top
Not by scripting. Everything in the widget/gadget is in a single group. THe button I simply set to an Object Controller in the properties dialog, set it to "Destroy" and for the object or group I set it to the group.
Reply #3 Top
Ah!
You will either have to use a script to issue Widget.Close or set the object type to "Widget" (in the object properies dialog) and then choose "Widget Close".

Even though you hide or delete the objects, DesktopX (or the Widget) will still keep running.
Reply #4 Top
Changed it to widget and widget close. Still does the same thing. Closes the app, but the process is still running.

Also created another object, set it to text and the text was "__" (w/o the quotes.
Gourped it & everything. Set it to widget & minimize.

It does nothing...

MUST I have a mouse down or up state added (but maybe not defined) for this to work? I have it set that way for the Widget Close, but as I said the process is still running even though the app is closed, but at least it does *something*.

Brain21
Reply #5 Top
hm.. I have not had such problems. It has been working fine.

Set it to widget & minimize.

It does nothing...

Is then when it's compiled and run as an exe? The Widget commands won't do anything as long as it's being hosted by DesktopX.

You might want to email support@stardock.com
Reply #6 Top
Compiled and run as an .exe, but the machine it is running on has DX running (I do have a guinea pig though that does not have DX on it).

Brain21
Reply #7 Top
What about widgets other people have made? does the same thing happend then?