DesktopX 2.4x bug reports

No..not us?

from WinCustomize Forums

Let us know which "undocumented features" in the latest DesktopX builds you've run into.

Please make sure you let us know which precise version you're running (i.e. released version, beta, or alpha).

Thanks!

14,092 views 23 replies
Reply #1 from WinCustomize Forums Top
I have noticed a few bugs while using DX.

1. My meters randomly decide to reset to their "default" red and green look on boot. This also changes the size of the meter from 8px wide to 50px.
2. I'm not sure if this is a DX bug, but it's been driving me nuts. If I code a Msgbox() in a script I'm working on, it doesn't show all the information I write to have displayed in it. It will display one line and just have blank space after that.
3. I've noticed a lag while DX is thinking. Could just be a scripting problem on my end.

DX 2.40f[a].002
Reply #2 from WinCustomize Forums Top
One bug I have seen twice now:

The system tray icons for the "Core Weather V1.01k" and "GT3 digital clock" just appeared unrequested for some reason (in the sys-tray).

The settings in properties for widgets are all default (normal z-order, accessibility = none, no shadow, no hue shift adjustment through slider - I do use the author's "click to change color" option).

Both instances of this bug seem to have happened shortly (not immediately) after I changed a Windowblind and Wallpaper to get a look at that combo, then back again to the Windowblind and Wallpaper I normally use.

Running DX version 2.40.035.
Object Desktop - Get all of our enhancement utilities in one suite
Reply #3 from WinCustomize Forums Top
I'm not quit sure this fits but I've found that a Microsoft Antispyware scan pretty much drags my system to a halt if DX is running. With DX unloaded, it's still slow but useable.
Reply #4 from WinCustomize Forums Top
The only widget bug I'm still aware in the last alpha I'm running is the currency widget not working (freeze saying "updating"). Apart from this, the last alpha made rework lots of widgets that the official 2.4 release did broke.

As for theme, I'm running Airlock and at startup, it shift all widgets from their location to 150 pixels right ... Pretty strange behaviour.

Garry : with or without DX, MS antispyware is not slow (I've just start a scan while running DX and typing this internet message, and I do not see any difference). So it should be related to your PC and not DX.
Reply #5 from WinCustomize Forums Top
I cannot modify the performance meter entry for an object after it has been 'set' the first time out.

I want a text representation of the send/receive traffic on a nic. Create an object associated with a performance meter (network interface) display it as text. It's all good. (I know you're asking what's the problem?) Well take that object and clone it. (I have 2 interfaces on the note book wired and wireless). Now go into the clone and attempt to configure the the perf meter to use the second interface...

An error dialog appears "Unable to connect to machine". Hit the OK and the 'select performace meter' dialog appears. However, no matter which meter is selected next only the first meter ever configured for the object is used. I get the same behaviour when attempting to access the orginial object.


I'm using DX 2.40f[a].002 on XP Pro.
Reply #6 from WinCustomize Forums Top
I'm using the perf meter to monitor %Processor time. On boot/reboot, the object's properties are set at default (data source of drive space, update speed of 200 ms). All of the changes in the appearance tab are also lost.

On restarting DesktopX from the tray, the object does not display the expect behaviour. Deleting and importing the object may or may not display the correct behaviour. Loading from a saved theme displays the correct behaviour.


I'm using DX 2.40f[a].002 on XP Pro.
Reply #7 from WinCustomize Forums Top
DesktopX loses information about object grouping on reboot. When selecting a previously grouped set of objects and moving them, one or more objects from the grouping are left in the original location. Listing the object using the 'list objects' item from the tray menu, reports the correct information. Opening the properties of the offending objects (the objects that did not move to the new screen location) and reapplying the group information results in the expected behaviour.


I'm using DX 2.40f[a].002 on XP Pro.
Reply #8 from WinCustomize Forums Top
After a shutdown or reboot request has been made to the computer, DesktopX appears to be taking an excessive amount of time to exit. An O/S dialog "DesktopX is not responding" appears with the choices End Now and Cancel. The dialog disappears before progress bar reaches the right side of the dialog, so I do not need to interact with the dialog.

I'm using DX 2.40f[a].002 on XP Pro.
Reply #9 from WinCustomize Forums Top
After changing screen resolutions... DesktopX does not return objects to their original screen locations. Display a grouped object containing multiple objects. Change the screen resolution from high res to a lower res where the some or all of the grouped object will not be visible on screen. Reset the screen resolution back to a higher res. Some or all of the objects in the grouped object appear on the left side of the screen rather than the expected position.

I'm using DX 2.40f[a].002 on XP Pro.
Reply #10 from WinCustomize Forums Top
DesktopX crashes with a memory access violation Smart Exception Report included...

Create an new object with defaults. Got to the states tab of the object properties and and change the appearance to text. Select the 'Mouse away' from the state list and click the remove button. Click yes in the confirmation dialog. Click the apply button of the object properties dialog. Crash.

I'm using DX 2.40f[a].002 on XP Pro.

Stardock SmartException Logging Information
-------------------------------------------

OS Version : Windows XP
Video Card : ATI MOBILITY RADEON 9600/9700 Series
Application Exception code: C0000005 ACCESS_VIOLATION
Crash Addr: 004301E6 01:0002F1E6 C:\Program Files\Stardock\Object Desktop\DesktopX\DesktopX.exe

Processor Registers (x86):
EAX:00000000
EBX:000000B5
ECX:00000000
EDX:00B438A0
ESI:0012C7E0
EDI:7C809A39
CS:EIP:001B:004301E6
SS:ESP:0023:0012C6B0 EBP:01C405B0
DS:0023 ES:0023 FS:003B GS:0000
Flags:00010246


Current Application Call Stack:

Addr Frame Logical addr Module Name
---------------------------------------------
004301E6 01C405B0 0001:0002F1E6 C:\Program Files\Stardock\Object Desktop\DesktopX\DesktopX.exe


Debug information for each stardock app follows ....
Reply #11 from WinCustomize Forums Top
Gaday People, for the last few weeks my weather programs with DesktopX 2.4 have been showing N/A for the current weather conditions,(Sydney, Australia. ASXX0112). I also have Sysmetrix running and it doesn't have the same problem but it uses the code YSSY for Sydney airport. All the other locations seem to work ok, is the problem with Weather.com (sent them an email but no reply as yet?) or the code? Is there another code or somewhere else I can get the info and still run it through DesktopX? I really love having up to date weather info and forecasts, this problem has been on going for a while now and is very frustrating. Any help or advice would be much appreciated.
Reply #12 from WinCustomize Forums Top
I can reproduce this DesktopX crash consistantly on several machines both at home and at work, running different themes.

Both machines are running WinXP SP1 and DesktopX 2.40f[a].002

Running Airlock at home, and I can't remember which one at work, but was able to do it with the Incredibles, and ANY desktopX theme that has that big bar area on the left-hand side of the screen. Don't know what it's called, but you know the bar that has the SysMetrix-like info in it, you can click on links marked "Internet" or "graphics" (or whatever you config it to, but these come setup with these by default).

Anyway, here are the problems:

1) Can move individual objects, but not the background object, or the whole thing.
2) Outlining to whole thing in order to select it and right-clicking and clicking on Group doesn't seem to do anything. I still can't move it as a group. As soon as I click somewhere else (thus removing the "selected" highlighting), I can move the individual objects in the sidebar again. IOW, the right-click group just doesn't seem to work with that at all.
3) Changing the move value from locked to normal or default often causes desktopX to crash & exit
4) Highlighting everything as a group, grouping it, and then attempting to change the Z-Order often crashes DesltopX hard as well.
5) I have managed, on a few occasions, to move and/or change the Z-order on the desktop. Not sure what miracles ocurred or how the stars were aligned in order for me to do things like change the z-order, click apply, and not have DesktopX immediately crash, but I have. Here are the results. Let me know if they are NORMAL:
a) Always on top - self explanatory
b) Normal - problem with this is that if I then open a web browser, when the window opens up it no longer takes up 90% of the screen as it normally does when not maximized, but it opens up smaller so that the side bar thingy (what IS it called, BTW?) is not covered. up. Kind of annoying.
c) Desktop - causes the grouped object (and I think the same thing happens if it is not grouped as well, depending on the object) to just completely disappear from the desktop at all. I assume that this is not the desired action since when I set the silver clock objeck in the airlock theme to "Desktop", it basically acts lik an icon in that everything can go over it and cover it up, and opening up programs will not try to avoid pixelk collisions with the object.
6) Get that side bar to where I like it (or at least can tolerate it), and I reboot the machine or logout and back in or something like that. When I get back to it, that sidebar thingy has moved down the left-hand side of my screen so that what was the upper-most portion of it is now just barely above my Start bar. Of course as discussed earlier, I can't just group the objects and move them back or anything...

Now, all these things happen, and most of them cause DesktopX to crash & exit, but ONLY to that big sidebar/longhornlooking thisg on the left-hand side of the screen. Perform these actions on a NORMAL desktopx object does NOT cause any of these problems.

So what's going on here? This is making it near impossible for me to configure and use DesktopX in the manner that I would like to!javascript:editor_insertHTML('ucCommentForm_comments_txtBody',' ')
javascript:editor_insertHTML('ucCommentForm_comments_txtBody',' ')

If you want to see any of the crash logs, just tell me which task described you want a crash log for and I will generate one right away (cause it's so easy to just kill desktopX cause it seems so fragile an app) and send it to you.

Thanks Brain21
Reply #13 from WinCustomize Forums Top
Another thing...

I have ObjectBar running at the top of my screen.

Whenever I lock my PC and then unlock it, basically the ObjectBar appears and then pushes down the big sidebar thingy. That is, it pushes it further down the Y axis on the left-hand side of the screen. After locking & unlocking my PC a few times, it is at the bottom of the screen, and I can't access it w/o unloading & reloading desktopX.

What is going on is that the space that the ObjectBar takes up displaces the vertical positioning of the sidebar. When I unlock the PC the Object Bar appears again, and displaces it AGAIN. Everytime.

Yes, I have the sidebar position/movement set to "locked"

I also does this with any other DesktopX widget that I have on the screen. I have one widget set to locked & always on top. It sits over my Object Bar. I lock & unlock and It has moved down vertically the distance of the height of the object bar.

Everytime I unlock the PC (many times a day) I have to reposition all DesktopX Widgets, including the Weather & Calendar widgets on my 2nd screen (running dual monitors). Very annoying!

Brain21
Reply #14 from WinCustomize Forums Top
This one is not recent but all email checker plugin-using object causes DesktopX to use 100% CPU eventually.

This script is in a object that is contained in a parent object. Bug comments within source code. This one is from the most current version.

'Called when the script is executed
Dim Thirdsize
Sub Object_OnScriptEnter
Thirdsize=object.Height/3'get 1/3 object size.
End Sub

Function Object_OnLButtondown(x, y)
object.top=-Thirdsize 'change to clicked mode. this code, somehow also moves parent object up at same distance as this!

End Function

Function Object_OnLButtonUp(x, y, Dragged)
object.top=0 'reset to normal mode from clicked.
End Function

Sub Object_OnMouseEnter
object.top=-(Thirdsize*2) 'change to hover mode.
End Sub

Sub Object_OnMouseleave
object.top=0 'reset back to normal mode from hover.
End Sub

I had sent the example object and discription to stardock support, but no reply after a week.

Edit: I checked out code again and found out it was wrong code being pointed out as bugged! I changed it to right one now.
Reply #15 from WinCustomize Forums Top
Running 2.40f[a].002

Unable to save a dx theme.

Steps to repro:

1. Right-click tray icon and choose Save or Save As (or choose "Configure DesktopX" and select Theme>Save As)
2. Observe Dual-Monitor info dialog. Click Yes.
3. Save Them as... dialog opens with desired path and filename already filled in.
4. Click Save.
5. Try to load theme, or do another Save As and Browse...notice the previously saved theme does not exist.

If the experiment is repeated doing a Save As/Browse and then an existing theme's name is chosen, the existing theme is deleted. Not overwritten - deleted. No overwrite warning - it just vanishes.

I've put a lot of work into my current theme, and I can't test other themes because I don't want to lose my current theme. If I just copy my C:\Documents and Settings\
Reply #16 from WinCustomize Forums Top
I changed code so it works better, but it still displays the same darned bug. The random height code was to test if it moves up or down on its own. Apparently not. It's ONLY when I click on it and it changes code that it moves up or down the parent object. BTW object visibility changes was to test if it was a accidental drag. No such luck.

I tried to uncontain the object, then changed it to stand-alone (no parent) and the code works well.

Dim Thirdsize
Sub Object_OnScriptEnter
Thirdsize=object.Height/3
Object.SetTimer 12311, 10
End Sub

Function Object_OnLButtondown(x, y)
object.Visible=False
object.top=-thirdsize 'moves up or down the parent object too. grr.
object.Visible=True
End Function

Function Object_OnLButtonUp(x, y, Dragged)
object.Visible=False
object.top=0
object.Visible=True
End Function

Sub Object_OnMouseEnter
object.top=-(Thirdsize*2)
End Sub

Sub Object_OnMouseleave
object.top=0
End Sub

Sub Object_OnTimer12311
object.top=-rnd*object.Height 'cool show, it works ok too.
End Sub
Reply #17 from WinCustomize Forums Top
I changed code so it works better, but it still displays the same darned bug. The random height code was to test if it moves up or down on its own. Apparently not. It's ONLY when I click on it and it changes code that it moves up or down the parent object. BTW object visibility changes was to test if it was a accidental drag. No such luck.


Try and return true to both Object_OnLButtondown and Object_OnLButtonup to disable default processing. I've not tried if it works. However if you change the object position between them, it could fool DX and think the object has been dragged, since the relative mouse position changes.
Reply #18 from WinCustomize Forums Top
I have a problem with widgets on DesktopX v 2.40f[a].002 and Win Xp home + sp2. If the widget have a activeX control like desktopx edit control and the control is resized/visibility changed and I go to properties of the widget and do enything there the controls change to state that they were while runed the widget, but their scripts are not reloaded so if I put msgbox in sub "OnScriptEnter" it wont execute after this. And if I set SUB OBJECT_ONSIZE(WIDTH, HEIGHT) and meke the control resize if it is in diferent size then it must be it often crashes. I have to make a timer so it will change the size back after 0,0005 second and this works.
This is example of the code:

'THIS DOESNT WORK:

Sub Object_OnSize(width, height)
If object.width <> desktopx.Object("MJM_RUN_back2").width Then
object.width = desktopx.Object("MJM_RUN_back2").width
End If
End Sub

'AND THIS WORKS:

Sub Object_OnSize(width, height)
If object.width <> desktopx.Object("MJM_RUN_back2").width Then
object.SetTimer 1,5
End If
End Sub

Sub object_ontimer1
object.width = desktopx.Object("MJM_RUN_back2").width
object.KillTimer 1
End Sub

object is the activeX control and MJM_RUN_back2 is a normal object
Reply #19 from WinCustomize Forums Top
I have several of these same problems.

I have not check but the last time i attempted to make a systray, or taskbar with a background other then the default, it would not work, the image in the bg would be gone, and most of the icons wouldnt show up.

I have had the same problem with the meters giving me the "cannot connect to machine". That is VERY Frustrating.
Reply #20 from WinCustomize Forums Top
I was moving a download meter and got the dreaded blue screen - first time that happened.
Reply #21 from WinCustomize Forums Top
I decided to totally rewrite the code to see if I could escape this weird bug, but still no luck. Button object (this script belongs to Button) is contained by object named ButtonBack. I need all 3 states to be in same picture, so I designed it so picture moves up or down to proper state. The problem is that when it moves up to proper pressed state, it moves ButtonBack up by same amount! Very, very annoying.

To recreate this problem, just create a solid magic pink picture of any size, use this for ButtonBack. Create a object named Button and make it a contained child of ButtonBack. Add this entire script to Button. If you want button to be square, make sure picture assigned to Button is 3 times as tall as it is wide.

When it's done and script is running, mouse over it. It should change (if you made Button picture solid single color you can't see it change.) to hover mode. It doesn't move parent up however. Now, press left button and hold. It changes to clicked mode, and somehow moves parent object up too. Let mouse button go and it stays there but it changes to normal mode.

Things I have tried:
Another object on front accepting clicks and sending messages to change state. No luck.
Timer that checks for a var that changes to 1 then changes to pressed state. No luck.


'Called when the script is executed
Dim Thirdsize
Sub Object_OnScriptEnter
Thirdsize=object.Height/3
Desktopx.Object("ButtonBack").width=object.width
DesktopX.Object("ButtonBack").Height=Thirdsize
End Sub

Sub Object_OnStateChange(state)
If state = "Mouse down" Then
Controlmode 1
ElseIf state = "Mouse up" Then
Controlmode 0
ElseIf state = "Mouse over" Then
Controlmode 2
ElseIf state = "Mouse away" Then
Controlmode 0
End If
End Sub


Sub Controlmode(Mode)
' Mode 0: normal; Mode 1: Click; Mode 2: Hover
If Mode=0 Then
Object.top=0
ElseIf Mode=1 Then
object.top=-Thirdsize
ElseIf Mode=2 Then
object.top=-Thirdsize * 2
End If
End Sub
Reply #22 from WinCustomize Forums Top
I'm not sure if this is an undocumented feature, but I am having a problem with adding sounds to my objects. In the past they have all worked great, but since I updated from DX 1.0 I can't seem to get them to "play" unless I hold my mouse button down on the object. If I release the button my sounds stop. I currently have 2.40f[a] DX. I have been using very short, and simple .wav files. ie: Bender from Futurama, "Bite my shiny metal ass", and the like. Oh, and my animations get whacked out when i update as well. just a couple of weird issues I've come across, thanks!
Reply #23 from WinCustomize Forums Top
I decided to totally rewrite the code to see if I could escape this weird bug, but still no luck. Button object (this script belongs to Button) is contained by object named ButtonBack. I need all 3 states to be in same picture, so I designed it so picture moves up or down to proper state. The problem is that when it moves up to proper pressed state, it moves ButtonBack up by same amount! Very, very annoying.


I don't understand why you have this requisite: >I need all 3 states to be in same picture
I can try fixing the bug - DX is probably detecting the changed mouse position after movement (between a down and up event) as a mouse dragging, however it is really a dirty solution, since with DX3 you can just use scriptable animations.
Have all "sub-states" as frames in one single state and use Object.CurrentFrame.