You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pivot.apache.org by "Todd Volkert (JIRA)" <ji...@apache.org> on 2009/03/26 16:09:50 UTC

[jira] Updated: (PIVOT-40) Interaction issues with Pivot and native modal dialogs

     [ https://issues.apache.org/jira/browse/PIVOT-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Volkert updated PIVOT-40:
------------------------------

    Attachment: screenshot.png

> Interaction issues with Pivot and native modal dialogs
> ------------------------------------------------------
>
>                 Key: PIVOT-40
>                 URL: https://issues.apache.org/jira/browse/PIVOT-40
>             Project: Pivot
>          Issue Type: Bug
>          Components: wtk
>    Affects Versions: 1.1
>         Environment: All
>            Reporter: Todd Volkert
>            Assignee: Greg Brown
>            Priority: Minor
>         Attachments: screenshot.png
>
>
> What steps will reproduce the problem?
> 1. Create a PushButton with a tooltip
> 2. Wire up a Swing file chooser dialog to the button (see code below)
> 3. Click the button
> {{{!
> pivot.wtk.PushButton button = (pivot.wtk.PushButton)serializer.getObjectByName("button");
> button.getButtonPressListeners().add(new pivot.wtk.ButtonPressListener() {
>     @SuppressWarnings("deprecation")
>     public void buttonPressed(pivot.wtk.Button button) {
>         java.awt.Container displayHost = button.getDisplay().getDisplayHost();
>         javax.swing.JFileChooser fileChooser = new javax.swing.JFileChooser();
>         fileChooser.showSaveDialog(displayHost);
>     }
> });
> }}}
> What is the expected output? What do you see instead?
> The display host does not see any mouse activity after the [modal] file
> dialog is opened, and as such, the tool-tip timer activates the tool-tip
> incorrectly.  The button also does not repaint itself as it should.
> See attached screen shot.
> We don't want to cater to deprecated use cases, but I'm wondering if there
> isn't a native event we could listen for in DisplayHost (like
> enabledChanged) that could allow us to easily solve this problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.