Possible nasty bug found in DesktopX

from WinCustomize Forums
I was working on the project for a while. I was exporting backups just in case the beta crashed. Well it finally happened. I think it was related to the file dialog replacement by stardock. Anyway...

The project was in pieces. I thought "No problem, I just recently made an export." and killed the pieces. I then imported the exported file. Guess what? It contains just one object. Luckily, this one has the highly complex script for my project.

But I have to remake all the other objects. Oh well.
desktopx
4,077 views 5 replies
Reply #1 from WinCustomize Forums Top
I found and tried a pre-3.0 file of the project and it had everything. Definitely a DX 3.0 bug.
Reply #2 from WinCustomize Forums Top
*cough*

My brain really needs tune-up. I didn't notice that "export as single object" or "export as a object and related".


Oh well. My project is recovered and making a decent progress. It's too bad without certain bug fixed and new feature: changing font of text object, it won't be finished.
CursorFX - Customize your Windows cursor
Reply #3 from WinCustomize Forums Top
I second the feature of changing font by scripts.
Reply #4 from WinCustomize Forums Top
DesktopX 3 seems to be very buggy application yet - Text input problem with silika widgets, when shutting windows down without unloading first desktopx crashes and the next start windows blinds is damaged. and so on - would it not be better in such cases to wait a month a release a buggy less application?
Reply #5 from WinCustomize Forums Top
Gasetto, this problem was from my own mistake, not due to any bug.