Programmatic selection of child widgets? about fortitude HOT 3 CLOSED

I think I had this solved a while ago and forgot to close the issue. Sorry about that.

from fortitude.

@jdickey — thanks for reporting this! I know you closed it because you'd solved the issue, but I'm trying to be very careful to clean up any and all Fortitude bugs, and want to make sure I understand what was going on here.

The issue seems to be that something called #freeze on the Class that you passed in (the one assigned to menu_adder). Fortitude does lazy initialization of some data it needs on widget classes — in this case, a Hash of the class's needs variables — and stores it as an @ variable on the Class. If the Class is frozen, that blows up.

Did you ever figure out why and how that class was frozen? If it's Fortitude, or even if it's a very common framework that #freezes view classes, I'd be interested in seeing if I can work around it somehow…

Thanks!
Andrew

from fortitude.

I'm going to close this — I haven't seen this elsewhere, and calling #freeze on a Class is both an unusual thing to do and, in a general sense, not really safe: many libraries may depend on modifying a Class at runtime. (This is Ruby, not Java. ;) )

If you run into this again or know what caused this, and it’s something standard (or, god forbid, Fortitude itself) rather than an edge case, by all means, let me know, and I’ll fix right away!

from fortitude.