DX Request: Save multiple widget export information
Monday, October 3, 2005 by ExodusCrow | Discussion: DesktopX Wishlist
Would be possible to have DX save previously exported widget/gadget information? Currently it only saves the last exported widget in the registry. Could this be done easily with an XML file that would save multiple widget preferences? It would save information such as: Name, author, path, icon, version, etc, and could be accessible when you export a widget/gadget. I envision a combo box titled "Previously exported widgets", with a list of widgets. Select the widget and all the appropriate fields are filled in with the information.
I would LOVE to see this feature, and not sure why I've never seen a request for it before.
Thanks for reading,
ExodusCrow
I would LOVE to see this feature, and not sure why I've never seen a request for it before.
Thanks for reading,
ExodusCrow
rabidrobot
Reply #2 Monday, October 3, 2005 7:52 PM
Reply #2 Monday, October 3, 2005 7:52 PM
I think the whole export process / dialogue could be streamlined. Storing of previous value sets would be a great additional feature.
ExodusCrow
Reply #3 Monday, October 3, 2005 10:33 PM
Agreed.
Reply #3 Monday, October 3, 2005 10:33 PM
| I think the whole export process / dialogue could be streamlined |
Agreed.
MountainDragon
Reply #4 Monday, October 3, 2005 11:14 PM
Reply #4 Monday, October 3, 2005 11:14 PM
By the way, has anyone had success with the DesktopX.HostType call? I tried to use it to determine whether widget.close would be appropriate, but it seems to return 0 in an object in builder mode, a widget, and a gadget.
ExodusCrow
Reply #5 Tuesday, October 4, 2005 10:28 AM
Reply #5 Tuesday, October 4, 2005 10:28 AM
MountainDragon: Haven't had time to try it out. Been trying to figure out object controllers and popup menues. I just can't get my head around them!
MountainDragon
Reply #6 Tuesday, October 4, 2005 10:52 AM
Reply #6 Tuesday, October 4, 2005 10:52 AM
The thing about pop-up menus is that they don't register as part of the object for mouse events, so they are an imperfect solution to the problem, if you're trying to respond to that.
I've messed around with object controllers but I find it just as easy and more flexible to script it myself, using the Visible attribute. I also tried using Opacity a bit, but found that bad things happen when changing Opacity from a script (repeatedly or with many objects). Not sure what that was about.
I've messed around with object controllers but I find it just as easy and more flexible to script it myself, using the Visible attribute. I also tried using Opacity a bit, but found that bad things happen when changing Opacity from a script (repeatedly or with many objects). Not sure what that was about.
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
Reply #1 Monday, October 3, 2005 7:46 PM