DX Questions - Ontop - System Prefs - Version - HELP SD!!!

"borrowing" = learning in your world?

So much becomes clearer.    

Love ya BFF..

Anyone other than Zu out there????

For the first question if you use a base object why not just use a variable and the Object.OnTop namespace? Or better yet, maybe set a boolean value with false being normal and true being OnTop? Something like below could be easily adapted to a form combo box.



For your second question maybe look at the Shell.Application object but, I'm not sure how this might be with Vista?

Edit: I'd like to see an Object.OnBottom namespace added. This could come in handy sometimes.

SirSmiley,

Ok, once something is made "ontop" how do you undo that? There is nothing that i can find to do that. Except in the Preferences dialog box, that z-order. Thats what im looking for.

Im not sure about the shell.application? where/what is that?

opps.. meant to add.. Thanks for the ideas.

I once asked Alberto (dx dev guy) whether we could have the always-on-top property scriptable and he said "sure", he probably just needs reminding

As for the version info etc - put some constants at the top of your script that match what you will enter in the fields when you export it.

Umm...forget the OnTop idea it just changes or positions the object to the top of all the other DesktopX Objects/Layers. It was worth a shot.

The Shell.Application object exposes some features of the Windows Shell to script. A good example is you can move/delete files and display the standard dialog you would get from the right click menu. Hope that helps.

Here's a MS link: Scriptable Shell Objects

Been there one that.. i just want to try and only have it in 1 place, and since im entering it when i export, why do i have to put it in my code too? Lazy? no, i just want them to match.



Ok, i was just thinking you found some other use for that with the DX widget.

Anyone from SD Dev out there?

You can fake a nearly-always-on-top solution by using a timer that repeatedly calls Widget.OnTop




Sometimes you just gotta roll with it

Sorry I couldn't be more helpful, dx is an intricate web of functionality and compromise

you got that right bud.. its all good.. it will work out somehow.. who knows.

i would LOVE to see someone from the dev team look at this and give us a "no" "yes" "possible" on these.. ANYONE???

Also.. the System tray/task bar does not seem to work when you export things as a GADGET.. is that the norm, because that not good. HELP?????

I was thinking about object on top and script control.I came to this conclusion.If you
create object a set at normal, duplicate it, set at ontop, then, control visibility any way you wish, and, you should be good to go.

Why isn't it easier to see, I'll never know, it just came to me now. Weird.

Good Luck Eddie

Jingles, that doesn't work. Tried your suggestion a number of different ways and none of them controlled positioning of the widget from script.

OOP'S  

I realize this post is sort of old, but I think I found a work-around for changing Z-Order. As long as your widget or group is has movement locked, then this should work well (you could probably even do it with a movable object with a little more script).

You have two/three base objects with a transparent 1x1 image (not no image at all, as this seems to make everything act weird on Always on Top), each object with a different Z-Order setting through the DX GUI editor. When you want to change the Z-Order, just set the parent of all the children objects to the base object that you want, and make sure that you aren't changing the parent of the children of those children, etc. The whole widget should be at a different level now.

If you want to allow the object to be movable, you could just make the position of the second base object equal to the first base object before transferring the children (I haven't tried this yet, though).

Hopefully Stardock will realize at some point that it would be great if you could directly change the Z-Order through script, however...