Frogboy Frogboy

DesktopX 3 Beta Reports

▼

DesktopX 3 Beta Reports

Limited beta reports..

from WinCustomize Forums

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.

beta
60,816 views 73 replies
Reply #51 from WinCustomize Forums Top
thomassen,

No WindowsFX here. I unloaded everything I could from memory and got TaskMan down to 16 total processes. I saved WindowBlinds 4.50e(b).002 for last. When I unloaded that beta version of WB, the drag-crash issue in DesktopX went away.

I need to add that I am using Windows XP Pro, SP2.

Non-Windows processes I killed, in no particular order (in case anyone is interested in the environment):
ProcessGuard 3.150
TrojanHunter 4.2
CursorXP (full version)
Diskeeper 9 service
OuterTech CpuUsage
Zone Alarm 5 Security Suite
ObjectDock Plus 1.11.009
sdmcp.exe
and...
WindowBlinds 4.50e(b).002
Reply #52 from WinCustomize Forums Top
Strange. I have the same WB version, but it didn't cause any problems on my system. I might have a deeper look into it tomorrow.



Feature request:
It'd be nice if the Object Lister would have a treeview to the left in the window and when you selected an item in the treeview it'd only list the child and related objects of that item.
Groupy 2 - Organize multiple applications into grouped tabs on your Windows desktop
Reply #53 from WinCustomize Forums Top
Feature request:
It'd be nice if the Object Lister would have a treeview to the left in the window and when you selected an item in the treeview it'd only list the child and related objects of that item.


I second that. I'd also like to see some sort of "numbering" system in the object lister.
Reply #54 from WinCustomize Forums Top
Another feature request:
Have a dropdown box at the top of the script editor that contains a list of all the functions in the script. Would be very useful for longer scripts.
Reply #55 from WinCustomize Forums Top
bug report:
I was making popup menues in JScript. All though the disabled menuitems where disabled, they did not look disabled.
Reply #56 from WinCustomize Forums Top
o dear...

I was using the 2.98 pro beta without any problems for over a week. Yesterday I uninstalled it and installed the 2.99b[b].003 version available on sdc - bad move on my part. Spent more than a few hours today working on a script, I went to adjust the text properties of a seperate object, dx builder crashed. On restarting dx the script was gone, just gone. Away. Well, ok, not quite. There was still a script, unfortunately it was entirely empty.

Looks like it's back to the old regime of exporting the object after every single change "just in case".
Reply #57 from WinCustomize Forums Top
Tiggz. DX keeps a "backup" copy of scripts that it uses.
Check out C:\Documents and Settings\
Reply #58 from WinCustomize Forums Top
I have a couple of q's.

1. In DX2 there was a "quick" way to go from Authoring to User mode, how can that be done in DX3?

2. I am working on a new theme (dock mainly), and i have some preference that im adding it, but my question is, how can i TEST this in CREATE mode? In other words, how do i debug it???

3. I assume i have to make things into a widget in order to get the NEW preferences to work? I cant save something as a desktop theme, and the load it in "user" mode and see the preferences, i just see "delete".

Id like to be able to get this new dock done and up when DX3 comes out, but right now that doesnt look like its gonna happen.

Any help would be great!
Reply #59 from WinCustomize Forums Top
I'm using System.KeyState(vk) to determine if Shift and/or Ctrl is pressed. However, it some times returns the value 3. In the documentation it says the function return 0, 1 or 2. What is this last undocumented keystate? It's currently gives me some headacke because my script doesn't work as expected because of this.

What happends is this:








ActionState
Inital state0
Ctrl beeing pressed1
After Ctrl is pressed2
Ctrl beeing pressed3
After Ctrl is pressed0
loop
Reply #60 from WinCustomize Forums Top
I keep getting this same error code, every time I try to run the beta version, and I just tried a DX update for March 14, and still get the same error, and DX3 will not start.
Reply #61 from WinCustomize Forums Top
Jeff: we fixed it. It was an incompatibility with WB and/or WFX. Thank you for reporting.
Reply #62 from WinCustomize Forums Top
I still get that error when I'm running WinFX. (I just went to try DX 2.99c[rc].003. (I rebooted before I tried it.)) Works fine without WinFX. But it got no problem with WB.

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


Other issues:
Object_OnSetFocus and ObjectOnKillFocus still doesn't work when using JScript.

Disabled scripted menu items still looks enabled. (All though you can't click them.)
Reply #63 from WinCustomize Forums Top
DVG: That looks like it's crashing in the script host. You may need to reinstall MS scripting host in order to correct that. It looks like something may have corrupted it. Get it at : http://msdn.microsoft.com/library/default.asp?url=/downloads/list/webdev.asp
Reply #64 from WinCustomize Forums Top
Check out C:\Documents and Settings\\Local Settings\Application Data\Stardock\DesktopX\CurrentTheme


Cheers ExodusCrow, already tried that one

Never mind, it's re-taught me the valuable lesson to save often I had become complacent because dx has become very stable since the days when I first started using it.
Reply #65 from WinCustomize Forums Top
Thank-you pjpowell, I re-installed MS Script host 5.6, and that seems to have done the trick. Don'y know how it became corrupted, but, I thank-you for the link.
Reply #66 from WinCustomize Forums Top
DVG: seems that it may be related to DX after all. It would be strange that both you and me had poblems with the scripting engine after installing DX. See post #7.
Reply #67 from WinCustomize Forums Top
The Offset: 00013830 bug disappeared with the final release now.
-cheers!
Reply #68 from WinCustomize Forums Top
Thanks, Alberto. When I get back from my trip I'll try out the release version and report here, just to close the loop.

Jeff
Reply #69 from WinCustomize Forums Top
The release version has indeed fixed the drag-crash issue on my system. Thank you.

Jeff
Reply #70 from WinCustomize Forums Top
On restarting dx the script was gone, just gone. Away. Well, ok, not quite. There was still a script, unfortunately it was entirely empty.


I have now had this happen to me on multiple occasions. Very occasionally, after making changes to a scripted object, clicking apply or ok on that object crashes dx. On restarting dx the script is empty.

I now export my objects to dxpacks after every succesfull change just to be safe, it kind of interrupts the creative flow a bit tho
Reply #71 from WinCustomize Forums Top
Yay. That sounds scary. I don't want to loose my script which I've been working long and hard on. Glad it haven't happend to me yet. (Touch wood!)
Have you tried reinstalling Windows Scripts? Just incase there is something there that's wrong.
Reply #72 from WinCustomize Forums Top
I also had this problem in 2.xx. So I often copy the script to a txt file and create 3 diferent copys of object. In earlyier 2.xx I had a lot of trouble when windows vbs scripting engine just dissapeared after dx crash. I hope that 3.xx will be more stable.
Reply #73 from WinCustomize Forums Top

I shouldn't have jinxed it in that last post... Ok, it wasn't related to DX crashing, but I still managed to loose script and object I was working on. I accedential double clicked on a dxpack and DX loaded it. However it cleared all the objects I allready was working on. I thought I completely lost about 3 days work there. But it turned out I had exportet it before I started on a new object today. But that new object and script is now comepltely gone. I even spent the last one and a half hour looking for it with my recovery program, but no trace. (I actually slapped my head, thinking of what I said in this last post when I realised what happend.) Anyways, time to call it a day. Night'o!