You need to log in before you can comment on or make changes to this bug.
When not using multiple state buttons with widgets that are part of a toolset, the radio buttons are not persistant. was noticed with navigation tools. radiobutton has to be clicked even if it's marked. radiobutton is sometimes not marked after a map draw. with a Map, the map is inaccessible until a radiobutton is clicked. with a dynamic KeyMap, pan is always enabled uncless zoom is clicked, and the zoom radio turns itself on and off during consecutive pans without clicking radiobuttons.
Looking at it.
There's more than one bug on that one. - Dynamic Keymap state is now kept saved. - About Map, Paul was looking at it since it is related to button.php (I think). Any developement on this one Paul ?
I have not looked into the second part of this yet. There are some technical difficulties with it that I am hoping to spend some time thinking through. I had hoped that one Button class could handle all possible scenarios so that widgets would not have to worry about how the application designer wanted to set up an application, but it turns out to be a fairly tricky problem.
fix for 1.99
updated version to 1.99
working on this now ...
this appears to work in my tests ... need the full chameleon sample suite to test properly but for now marking as done.
verified using beta 2 2004-06-20 on Windows 2000 ie6, using the: http://localhost/chameleon/samples/sample_basic_plainbuttons.phtml
Verified on Fedora Core 1 Chameleon 20040625
