Zugg Software :: View topic - CMUD 226

Posted: Fri Jun 06, 2008 6:42 am

No matter what selection I make for the display filter, it is always set to ALL. Clicking on the differnt filters will select the them, but they re not applied.

EDIT: Just as suddenly, the filters began working again. So I don't know what caused the problem other that it started when I selected an Alias to be created and instead of displaying the newly created (blank) alias, it displayed the properties of the session window. This is not new to 2.26 though, it also happened in 2.25.

Posted: Fri Jun 06, 2008 5:31 pm

If you find a way to reproduce this, let me know. But this still sounds like something is corrupted in your package file.

Posted: Sat Jun 07, 2008 12:28 am

Well, as I said. It happens when one selects a new type of setting from the dropdown list. I am in the habit of clicking on the class folder I want the setting to reside prior to selection because of the bug in the previous versions that would create the setting in the root (session window) folder. After selecting the setting, instead of displaying an empty script box, the Editor will display the properties for the session window. No matter how many times I go back to the intended folder and click for a new setting this will continue to happen. The settings filters will not work and will be locked on ALL (though the clicked filter will be highlighted). Then it will suddenly start working again and my intended folder will contain a series of blank settings corresponding to the number of tries at creating the new setting. The peculiar thing about these blank settings is that when I try to delete one (since I don't need the extra ones), they all disappear. I don't know if this is reproducible at will.

Posted: Mon Jun 09, 2008 5:20 pm

I need the *exact* steps that you are using. Please treat me like an idiot and tell me *exactly* what you are clicking on and exactly what you are typing. For example:

1) Click on the Alias filter button to only show aliases
2) Click on an existing class folder
3) Then select Trigger from the New dropdown list
4) CMUD properly shows the trigger editor.

So it seems to work here, but without the exact steps that you are using, it's hard to reproduce the problem.

Edited: Also, CMUD *does* automatically try to delete blank settings when it can. Having blank settings in your session can cause lots of different problems, so just clicking on a blank setting and then clicking on a different setting will cause the blank one to get removed in most cases. So I think the behavior you are seeing with all of your blank settings getting deleted is normal.

Posted: Tue Jun 10, 2008 12:59 am

I am sorry, Zugg, I am not able to reproduce it because I am not sure what I did prior to this behavior by the editor. I will keep close watch and see if I can capture it. The invisible settings problem is not new, just rare. I've had instances before where creating a setting would just make the editor display the session window property as if one had clicked on the setting and eventually there would be a number of blank settings in the target class corresponding to the number of attempts at creation.
This time, I tried to filter the settings to determine where the created settings had landed, that's when I discovered that the filter was not working. So the two problems are related. As soon as I have new information, I will post it.