Ok, don't worry I understand. I didn't write any test for now. It is only a little prototype for suggestion.
On mié, 2011-09-14 at 14:08 +0000, Sandro Martini (JIRA) wrote: > [ > https://issues.apache.org/jira/browse/PIVOT-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104512#comment-13104512 > ] > > Sandro Martini commented on PIVOT-794: > -------------------------------------- > > Hi, thanks for the info (and I'm sorry but hadn't time to look at > pivot-stuff-validation ... have you put there some minimal test, too ?). > I'll try to merge all these features for BlockingDialogs for the 2.1 release > ... unless some objections. > > Bye > > > > Add BlockingDialog to WTK > > ------------------------- > > > > Key: PIVOT-794 > > URL: https://issues.apache.org/jira/browse/PIVOT-794 > > Project: Pivot > > Issue Type: New Feature > > Components: wtk, wtk-terra > > Affects Versions: 2.0 > > Environment: any > > Reporter: Thomas Guretzki > > Assignee: Sandro Martini > > Labels: patch > > Fix For: 2.1 > > > > Attachments: patches.zip > > > > Original Estimate: 0.5h > > Remaining Estimate: 0.5h > > > > I've written an additional BlockingDialog class which can host any Dialog > > outside of the normal HostFrame. > > This way, awt is used to do the {@link #open(Display)} in a blocking way, > > i. e. the flow of control doesn't return before the content Dialog is > > closed. > > The content can be set in the constructor or (e. g. via bxml) using {@link > > #setContent(Dialog)}. > > A small change to DesktopApplicationContext is necessary: static class > > HostDialog has to be given package access. > > -- > This message is automatically generated by JIRA. > For more information on JIRA, see: http://www.atlassian.com/software/jira > > >
