A few noticed bugs in 3.49[b].009

1. When trying to use the properties page (as I don't know where else to set this) to set an object as a child, once you select Yes DX will crash: AppName: desktopx builder.exe AppVer: 0.0.0.0 ModName: user32.dll ModVer: 5.1.2600.3099 Offset: 0002bae7

Objects that are already children seem to be fine, and when going back to the release version it allows this to be set correctly. Going back into the Beta and it crashes again.

2. the Object.Rotation namespace option seems to be a bit flaky. In the non-beta version it works fine, but the effect can be seen by loading sVis's NrG Clock (https://www.wincustomize.com/skins.aspx?skinid=957&libid=34). In the release version the clock is still, while in the beta it bobs back and forth in about 15 second circuits as the clock faces rotate.

3. When on my machine at home, which is an AMD platform, the graphical performance meters based on Memory do not seem to work. At work, which is an Intel platform, they work as expected. I am running 4 gigabytes of RAM at home on an XP32 system, however, so this may throw the counter a bit crazy. If there's any further testing I can do to isolate the problem, let me know.

While I've done some scripting and so forth previously, I'm still new to DesktopX building so please bear with me.

-Alyred
7,422 views 7 replies
Reply #1 Top
Hi
I'm running your home system with half the memory with no problems.
Try clearing your cache and reloading good luck  .

Reply #2 Top
I had problem number one but, switching into client mode than back into builder mode for some reason resolved it.
Reply #3 Top
Very Weird
I picked up the problem after leaving this page.SirSmiley's fix
worked just fine.But, I still beleive It's all related to the
Summary tab showing up as list veiw.

Reply #4 Top
Hmm, I'm unable to switch into client mode; as soon as I get the error DX crashes completely -- I have to reload it.

I'm of the same persuasion; it's probably the list mode that's causing the problem. Would be nice if there was another way to click to set this, like the ability to set the parent by right-clicking on the object.

Regarding the cache issue, I didn't think of that. I'll give it a shot, but I suspect there might be problems because XP32's max memory size is about 3.5 gigs, so it may be giving it problems with max amount of memory counters.

Thanks for the idea, though.
Reply #5 Top
1. When trying to use the properties page (as I don't know where else to set this) to set an object as a child, once you select Yes DX will crash: AppName: desktopx builder.exe AppVer: 0.0.0.0 ModName: user32.dll ModVer: 5.1.2600.3099 Offset: 0002bae7


happens to me also every time, had to revert back to previous working version.

The rotation is also an issue.. had a circle with earth/moon/stars in it, it rotates oon its center in 3.2, but in the beta it rotates and Moves 10-15 pixels in random directions. So bad had to go back to 3.2
Reply #6 Top
1. When trying to use the properties page (as I don't know where else to set this) to set an object as a child, once you select Yes DX will crash: AppName: desktopx builder.exe AppVer: 0.0.0.0 ModName: user32.dll ModVer: 5.1.2600.3099 Offset: 0002bae7

Objects that are already children seem to be fine, and when going back to the release version it allows this to be set correctly. Going back into the Beta and it crashes again.



Have you tried ensuring the object you want to be a child is within the co-ordinates (x,y,w,h) of the parent object before you select the option to make the object a child? Once done you may, if you choose, move the child object out the co-ordinates after successfully binding them together.

Tim


Reply #7 Top

The crashing issue is resolved in a build that has been released internally. To anyone experiencing this problem, please either hop on our irc server at irc.stardock.com, channel #stardock and find me there, or feel free to write in to support @ stardock.com

This build may also help with the rotation issue, but I have not done thorough testing myself.

AlyredB: Have you tried loading the graphical meters with the 3.2 build of DesktopX?

SirSmiley: Thanks for sharing your workaround. When I encountered this issue before, I hadn't thought to try that.

-Mike
[Stardock Support]