This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
What should be the behavior of an InputVerifier if you are transfering focus directly to a component in a differnet FocusCycleRoot? For example, I have an application frame (JFrame) in which multiple applications can be running (JInternalFrames). If I have focus on a field in one application, and switch to another application (ie focus xfers to a different focus cycle root - JInternalFrame) should the InputVerifier be triggered?
What happens is the InputVerifier gets triggered and fails (on bad input), the new JInternal frame is displayed on top of the old one, focus appears to transfer to the first component in the new app(it has a cursor), but when you type the component with the failed input verifier recieves the input. If you hit tab from the 2nd app, focus xfers to the next field, and it behaves normally after that. It's somewhat like the two fields are both sharing/fighting for the focus initially.
I would think that xfering focus to a different focus cycle should skip the input verifier. Because when you return to the original focus cycle, the focus will return to the field that had it before.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: problem using inputverifier while using multiple internalframes