Frogboy Frogboy

DesktopX 3 Beta Reports

DesktopX 3 Beta Reports

Limited beta reports..

For Widget/theme/object developers we currently have a small closed beta (if you want the beta, let us know what DX content you've created in a seperate thread and we will see what we can do).

For those of you in the beta of DesktopX 3, let us know in this forum what issues you're running into.

60,937 views 73 replies
Reply #26 Top
Not sure if this is really a DX3 bug or just the way Windows does things, but if a Widget.Preference("name").Caption is too long it pushes everything off the side of the window.
Link

Something to be aware of if your making preferences.
Reply #27 Top
finding the same thing as XX - when exported as a standalone gadget there doesn't appear to be a properties dialog so hue changing, shadows etc are unavailable as are the new widget.preferences
Reply #28 Top
Same problem here also.
Reply #29 Top
finding the same thing as XX - when exported as a standalone gadget there doesn't appear to be a properties dialog so hue changing, shadows etc are unavailable as are the new widget.preferences


You should have an option called "Standard preferences dialog" when exporting as a gadget. Maybe the public beta doesn't have that fully finished though. Gadgets will have all features as widgets in the final build.
Reply #30 Top
yep, I saw that checkbox, and so I assumed it must just be a bug in the beta
Reply #31 Top
Out of interest, those of us who have the DX3 beta, who will have widget/gagdets ready for the DX3 release?
Reply #32 Top
Are we supposed to hold back and not upload any until it's released?

Reply #33 Top
Well you don't want to release things made with DX 3 until DX 3 is available as they won't work on DesktopX 2.
Reply #34 Top
Some obscurities that should have been changed with the silica widgets/gadgets :

- RSS Reader doesn't work
- Drive meters show free space, not used space as they say. also the drive-text doesn't change with the drive
- Mail checker doesn't work when imported and I can't figure out why. (DX3 bug ?)

I am absolutely not sure if I like the strong separation between runtime and builder. At leeast there should be a fast switcher between the two in the final build. Other than that I like the direction DX is going. And finally we have promising new mail-checker opportunities.
Reply #35 Top
Also I would like to be able to have dx started in builder mode after reboot. the way it is now is not very good.
Reply #36 Top
New widgets are okay now, but I still can't get the mail checker to work in dx builder (?).
Reply #37 Top
Latest build :

I am loosing all my objects when switching from runtime to builder and vice versa. I am sure that was not intended (?)...
Also marking several objects at once doesn't work
Reply #38 Top
2.99b[b].003
When I try to add a systray object I get this message:
Stardock MCP not found or wrong version.
Systray support disabled
Reply #39 Top
I have two accounts on my computer. One that I use normally, and one I use for when I'm working with 3D Studio Max and such. On the latter one, DX3 works fine, but on the one I use normally I get an error message when I choose "Configure DesktopX..." from the systray menu. The DesktopX builder gives the exact same error when I even just try to launch it. This doesn't happend on my other account. I suppose it's a conflict with any other program I got running. ? I got WB, OD+ and WFX running on that account.


AppName: desktopx.exe AppVer: 0.0.0.0 ModName: directgui.dll
ModVer: 2.0.0.0 Offset: 00013830


System:
Dell 8300
2.8Ghz P4
1GB RAM
ATI RADEON 9800 128MB
WindowsXP SP2+
Reply #40 Top
AppName: desktopx.exe AppVer: 0.0.0.0 ModName: directgui.dll
ModVer: 2.0.0.0 Offset: 00013830


I get this in the public beta if I try to drag the "Configure" dialog in either the client or builder. If I leave the dialog box where it first appeared, then I can work in it OK.
Reply #41 Top
History for the most recent DesktopX beta stated "IconX should catch up those blank icons now", but icons such as "My Briefcase" are still loading blank on my desktop. I did a complete uninstall and reinstall, but it didn't clear it up.
Reply #42 Top
C242: On the DesktopX builder config, go to preferences and you can have the builder be the default program for handling desktops and such.
Reply #43 Top
Jeff - that's pretty strange. I can't reproduce it.
Reply #44 Top
I have the same with the builder. If it is in the "Welcome" tab and I click on the title bar I get similar crash. But in "Desktop"/"IconX"/"Preferences" tabs its OK
Reply #45 Top
Brad - let me see if I can isolate whether or not it's theme-specific and give you exact steps to repro.
Reply #46 Top
Brad - It's apparently not theme-specific. I loaded the new dev desktop and your simple longhorn desktop and I could duplicate the issue with both themes.

1. Launch DX3 in client mode.
2. Load theme.
3. Right-click tray icon and choose Welcome.
4. From the Welcome splash screen/dialog choose Create.
5. Observe warning about Builder needing the Client to close. Click OK.
6. Observe Builder configuration dialog appear.
7. Try to drag the dialog to another part of the screen.
8. Observe crash and error message from post #40.

My System:
P4 3.0 GHz w/HT
1024 MB RAM
4 very fast Ultra ATA and SATA hard drives
ATI Radeon 9800 Pro with 5.2 Catalyst drivers
Dual ViewSonic 19" LCD monitors (1 connected to the 9800's VGA output and one to the DVI output)

HTH,

Jeff
Reply #47 Top
Right but what you're saying is just moving the configuration dialog causes it to crash.  I can't reprodue that here.  I think it's probably specific to your system.
Reply #48 Top
Jeff: do you have WindowFX running? I got the same error as well, but it dissapeared completely when I unloaded WindowFX.
Reply #49 Top
I have run into a problem when using JScript. The function Object_OnSetFocus() and Object_OnKillFocus() does not trigger when using JScript. It does however when using VBScript.
Reply #50 Top
I can't reproduce that either.