Ok, no problem, I really didn't notice. Really sorry about that. I'll be
careful from now on.
Thanks for the add in the changeset but I suspect the problem should be
fixed somewhere else, I mean upstream since the value variable doesn't
receive the appropriate stuff. I didn't quite get where i
Thanks! This has been fixed in changeset 5594:2f84c42a548a.
Also, if I could ask for a minor thing to assist us with list
maintenance: when starting a new thread on the list, please create a
brand new email to galaxy-dev rather than replying to an existing
message. Replying includes headers that
Yeah, and I fixed it... somehow.
In the lib/galaxy/web/form_builder.py I added the import on
string_as_bool from galaxy.util, then I modified the code as follows:
126 @staticmethod
127 def is_checked( value ):
128 if value == True:
129 return True
130 # This
2011/5/23 Louise-Amélie Schmitt :
> @ Peter: I'm not sure I can get more precise... the checked attribute has no
> effect whatsoever, the boxes are always unchecked when I open the tool. I
> tried the "yes" and the "true" values to no avail.
>
> @ Leandro: Yes I already saw that ...
>
> But that's
@ Peter: I'm not sure I can get more precise... the checked attribute
has no effect whatsoever, the boxes are always unchecked when I open the
tool. I tried the "yes" and the "true" values to no avail.
@ Leandro: Yes I already saw that and tried to correct the code the way
someone suggested in
Not everything works correctly with checkbox booleans, the bug a couple
people and I reported long ago
https://bitbucket.org/galaxy/galaxy-central/issue/393/cant-use-checkbox-boolean-with-conditional
is still there.
2011/5/23 Peter Cock
> 2011/5/23 Louise-Amélie Schmitt :
> > Hello,
> >
> > I
2011/5/23 Louise-Amélie Schmitt :
> Hello,
>
> I know this is still not fully implemented and that there has already been a
> lot of messages on the topic, but I just would like to know if there's a way
> to make the "checked" attribute in the param tags have the required effect.
It might help if