DesktopX 3 Beta Reports

Limited beta reports..

Monday, February 28, 2005 by Frogboy | Discussion: Beta

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.

First Previous Page 4 of 4 Next Last
Alberto
Reply #61 Tuesday, March 15, 2005 5:23 AM
Jeff: we fixed it. It was an incompatibility with WB and/or WFX. Thank you for reporting.
thomassen
Reply #62 Tuesday, March 15, 2005 10:49 AM
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.)
pjpowell
Reply #63 Tuesday, March 15, 2005 11:43 AM
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
Tiggz
Reply #64 Tuesday, March 15, 2005 3:19 PM
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.
DVG
Reply #65 Tuesday, March 15, 2005 4:33 PM
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.
paxx
Reply #66 Tuesday, March 15, 2005 5:17 PM
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.
thomassen
Reply #67 Tuesday, March 15, 2005 8:10 PM
The Offset: 00013830 bug disappeared with the final release now.
-cheers!
JeffBDVS
Reply #68 Wednesday, March 16, 2005 5:13 AM
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
JeffBDVS
Reply #69 Wednesday, March 16, 2005 1:16 PM
The release version has indeed fixed the drag-crash issue on my system. Thank you.

Jeff
Tiggz
Reply #70 Wednesday, March 16, 2005 5:13 PM
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
thomassen
Reply #71 Wednesday, March 16, 2005 5:23 PM
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.
M.J.M.
Reply #72 Wednesday, March 16, 2005 6:04 PM
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.
thomassen
Reply #73 Wednesday, March 16, 2005 7:27 PM

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!

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!



web-wc01