I would like the ability to change the shortcut target of an object with script - this would be especially handy for folder objects. On the list for March, 1. Also, scrip
Alberto
VBScript and JavaScript. They don't need additional runtime components.
Some people are having problems with proxy, so I'd like to understand more about this. I did some tests while I was behind proxy and DX and widgets worked fine. The proxy settings were inherited from Internet Explorer settings. So, what problems are you experiencing? Do ALL objects that connect expose the problem? Some of them use the Web Browser ActiveX control, some of them just use the COM XML-HTTP object. Is it the same? What kind of pr
Another idea would be separation of objects and scripts. Basically, you make scripts and objects, then "assign" scripts to objects. That way. if you have 10 or even 100 objects using same script, good examples would be my apptlinearcalendear and Node Master. If the script has a bug and you just added it to 10 object, it's a long
It will be fixed in this week's build.
Do such problems still happen with 2.40f[a].002?
Are you using 2.40f[a].002? It should be fixed.
I can say my opinion based on technical aspects. I would say some fault of "Konfabulator has more polished widgets" is also because of some problems like: - Some of our widgets like Weather or Calendar were not so perfect. We updated some content for 2.4 and we'll make sure we have great boundled widgets in 2.5. - We are rewriting several documentation. Especially the Scripting manual, if you check the latest 2.40f[a].002 build, it has bee
We are still trying to track the cause of the problem with the new builds for some users. I tested the last DX and IX distribution on a clean box and it worked fine. I suspect it is Norton Antivirus blocking the script execution. We had a mechanism in place to avoid that, but maybe it changed in the last builds. Could you confirm that you have or not have NA in your setup? We are preparing some test boxes with NA on them to try today as well.<
The first two weeks were saturated by the following tasks (in order of effort): Stardock product activation This has been very complex in the end. The first problem has been designing a smart mechanism that does not expose evident flaws. I'm very happy about the actual deployment, though there are still areas of improvements, especially on the g
Tomorrow probably.
On Shae Petersen suggestion, we implemented bitmap masking in DesktopX. You basically can specify that an object is a "mask", and its children will be blended using the mask alpha blending values. Here is the new option: <img bor
Vector text One major feature of the upcoming DesktopX is the option to use vector text, that's basically simple text painted over standard objects. Previous text was bitmap based. Here is the new config option: <font face="Tahoma" s
DesktopX 2.4 release. After that, still quite a lot of work, mostly on fixes and the "engine" and scripting part. I believe the business success for DesktopX in the next two years will eventually live in the application engine itself more than the actual "DesktopX" product. Widgets are cool but not really good business-wise IMO. Maybe becau
It must have a double entry in the Startup folder. The first one loads DesktopX. The second one opens the config panel since DX is already running. Check into \Start Menu\Startup and into Regedit: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run Let me know what was the problem. Maybe there is a flaw into the installer.
Yes. The Enhanced version of IconX let you choose any PNG to assign in the place of the default icon. The Shareware version will let you apply the PNG, but it won't be remembered the next time IconX is loaded.
Feline. The hotkey idea is good and is in todo list. However I suggest to use the widget concept more, i.e. make your objects widgets (export->Widget). Widgets are not bound to the desktop. They are accessed via taskbar or systray just like apps. Object = desktop theme or desktop interfaces parts Widgets = stand alone independent applications
Solution design: what themes are showing this? Are you using the last beta?
The EXE should be around 5K larger than the .dxpack. All extra space is for the .ico inside the .EXE. About runtime memory used, that should be less in Widgets running stand alone, since you don't have the whole DesktopX workframe running. There are also lots of other benefits like instance isolation (if something crashes it won't bring down everything). All in all Widget stand alone mode is the best way to run these objects. DesktopX.exe main purpose now is as a development/authoring wo
Could it be IconX having problems with a desktop item? Unload DX, run regedit.exe and set HKEY_CURRENT_USER\Software\Stardock\DesktopX\IconX = 0, reload DX.
What do you mean? Only DX Professional-generated .EXEs contain the runtime files (3rd export option, Pro-only). Standard standalone widgets (2nd export option, Enhanced and Pro-only) use the installed DX runtime, though they still run as standalone. The first are obviously a bit larger, but it is only about disk space. Memory used is less than the one used in DX for both, but still, the runtime RAM space used by all three options (.dxpack, .EXE, Pro .EXE) is very small, and most of it depends on
Or just run IconXStartup.exe. It's built with that purpose in mind. Run again to show the configuration or unload.
Well, you can wait a bit until DX 2.1 is released. Then you can make the bar a true appbar. Old global workarea settings will still work but be obsolete. DX Appbars work 100x better.
It isn't currently possible to do in 2.0, since objects can't affect the work area or autohide. DesktopX 2.1 will natively support true appbars just like Windows' taskbar. It'll be very easy to via scripting like: Object.AppbarMode = 0 'undocked Object.AppbarMode = 1 'docked Object.AppbarMode = 2 'autohide That'll work for applications generated by DX Pro 2.1 as well.