The following issue has been updated:

    Updater: Morgan Delagrange (mailto:[EMAIL PROTECTED])
       Date: Wed, 10 Sep 2003 10:49 AM
    Changes:
             Fix Version changed to jface-1.0
             Fix Version changed from 1.0
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=JELLY-39&page=history

---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=JELLY-39


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JELLY-39
    Summary: [JFace taglib] PreferenceDialogTag parent patch
       Type: New Feature

     Status: Reopened
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

    Project: jelly
 Components: 
             taglib.jface
   Fix Fors:
             jface-1.0

   Assignee: james strachan
   Reporter: Christiaan ten Klooster

    Created: Thu, 27 Feb 2003 5:31 AM
    Updated: Wed, 10 Sep 2003 10:49 AM

Description:
allow <preferenceDialog parent="${applicationWindow.Shell}">

You need this if the preferencesDialog is in a separate file.

It would perhaps be better if 'findAncestorWithClass(ApplicationWindowTag.class)'
would return the ApplicationWindowTag. Then you can use 
<preferenceDialog parent="${applicationWindow}">

James, could you also add a taglib.jface and taglib.swt component in JIRA ?


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to