Component#isVisible() uses internally Component#isVisibleInHierarchy(), so it should just work. Or maybe I didn't understand you.
On Fri, Apr 20, 2018 at 3:25 PM, James Carman <ja...@carmanconsulting.com> wrote: > I have a scenario where a certain type of component should typically be > invisible, but in certain scenarios, it neeeds to become visible. That > visibility can be changed by anybody in its ancestry and the closest one to > the component should decide. Anyway, do we have established patterns for > this? Do I make the guys who want to control this visibility implement > some interface and search for them up the hierarchy? Is there a different > way? > > Thanks, > > James >
