From: Timothy W. <tw...@us...> - 2004-05-31 12:00:21
|
Maybe you could share what was the problem? On May 31, 2004, at 12:00 AM, Nirmalya Ghosh wrote: > On Sat, May 29, 2004 4:38 am, Timothy Wall said: >> The ClassMatcher does a simple match against components in the >> hierarchy (starting at the optional root given to >> ComponentFinder.find([Container,]Matcher). >> >> If it's a simple layout and all components are reachable via normal >> hierarchy traversal, I don't understand why it wouldn't be found. >> >> You could do the following to find out what is happening: >> >> getFinder().find(new Matcher() { >> public boolean matches(Component c) { >> System.out.println("Examining " + Robot.toString(c)); >> return false; >> } >> }); >> >> This will print out all components that are examined in the order >> encountered, until finally the ComponentNotFound is thrown. You >> should >> see the finder walk the hierarchy from your initial frame until it >> compares against your component. > > > Hi Timothy, > > Thankyou VERY much! > I can now test my GUI reliably! > The code listed above helped me figure things out pretty well.. > Once again , thanks a lot for your help. > > Regards, > nirmalya > |