Zugg Software :: View topic - CMUD 3.33 (and previous version) toolbar issues with colors

Novice Joined: 15 Jul 2010 Posts: 39 Location: USA

I created a bunch of buttons, some are multistate, some are single press, and some are toggle.

I setup the toggle buttons to be one color, and when pressed, the background color for the pressed state is a different color and the title bar changes (i.e. Off: Knee, On: "Knee On") so I can identify what toggle buttons are pressed and what aren't.

In every version of CMUD I run in Windows 7, the toolbars don't work properly. The buttons toggle and all the scripts run as expected, but sometimes the buttons change color properly, and sometimes they don't. Sometimes the button looks depressed, but doesn't change color, and when I click on a different button, the first button's color finally changes to what it is supposed to be. This has occured in every version of CMUD I have used and on every computer where I have installed CMUD, including creating the buttons from scratch (not importing my packages)

Right now when I click a multistate button, the entire button turns from grey with black text to black background with black text and becomes unreadable after I first click on it. The buttons functionality remains unchanged. I can still click the button and do everything it is supposed to do, but now I have 4 black boxes where my multistate buttons are so I can't tell which button is which without clicking on them. This has occured only on version 3.33 on windows 7 using an imported package that was functioning in 2.37.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

2.37 was 1)a really, REALLY long time ago and 2)full of bugs. I would never trust a package created and handled by 2.37.

That said, try checking to make sure your button color settings are really set. Black on black generally means they are not set (something that can occur during importing or copy/pasting), and I think each part of the multistate button gets its own color settings.

Novice Joined: 15 Jul 2010 Posts: 39 Location: USA

Yes, They do. I am thinking I will have to delete the entire package and create everything from scratch.

The other issue I am seeing with 3.33 is if I minimize it and leave CMUD alone for a while, at some point it stops coming back. It doesn't list as 'Not Responding' but it no longer restores/maximizes and I have to right-click the icon and 'Close Window' to terminate the CMUD app and re-launch it. I am going to test this behavior on a fresh session with no packages except the default and see what happens.

Novice Joined: 15 Jul 2010 Posts: 39 Location: USA

I don't know why, but I am stilling having the issue with minimizing CMUd and being unable to bring it back. This is occuring with a fresh session with a new package all created with 3.33 and nothing imported from 2.37.

Posted: Sat Jan 15, 2011 5:16 pm

My solution to the bringing back CMUD after minimize problem:
Ctr+Alt+Delete to bring Windows Task Manager
In Applications tab right-click on CMUD, click on Switch To.