~Are you using a recent version of desktopX ?
I have had similar problems in the past , but updating desktopx usually fixed any bugs. On rare occasions it was the update that confused things so rolling back to previous working version fixed the bug.
Im sure someone can offer futher advice on this.