On Feb 15, 2011, at 4:21 AM, Werner F. Bruhin wrote:
> Anyone has a tip on how I can cleanly not run into this?
I would just ignore it. It's another example of the downsides of the
multiple-UI design we used. And it's not an exception; it's really just a
warning. We tend to error on the side of being more verbose in our warnings
rather than hiding inconsistencies. Normally, trying to get/set Visible on an
object that doesn't have an underlying Show() method would be a programming
error; in this case, it's really not an error.
-- Ed Leafe
_______________________________________________
Post Messages to: Dabo-users@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message:
http://leafe.com/archives/byMID/285ce4e4-c1cc-4a66-b73b-fcc3e66e7...@leafe.com
