Re: (Bug?) JDev 9.0.3 / UI Debugger, no representation of JDialog within UI Tree

Raffael,

I already replied to your post on OTN:
  http://www.oracle.com/forums/thread.jsp?thread=164825&forum=83 As I said, I cannot reproduce the problem. I personally use the UI Debugger on JDev itself, including on JDialogs, and it works fine for me.
Try the code I posted on OTN and if that works, adapt it to reproduce the problem. That would really help me to find the problem.

dmz17,

Thank you for your help but I think you mixed up the UI Debugger and the UI Editor wich are totally distinct. The UI Debugger is a sort of WYSIWYG extension to the debugger for Swing developers. If you have a Swing application (or AWT) that you can debug by pressing the "debug" button, then all you have to do is to use the "Run>UI Debug" menu.

• Cedric JDev team

"dmz17" <dmz17_at_nospam.nowhere.com> wrote in message news:<pan.2003.02.27.22.42.53.551642_at_nospam.nowhere.com>...
> On Wed, 26 Feb 2003 05:29:46 +0000, Raffael Vogler wrote:
>
> > Thank you for your suggestion.
> > I'm not sure what you mean by saying "exposed".
> > I declared and initialized (JDialog jDlg = new JDialog()) the
> > JDialog-Object together with all the other Components within the
> > Main-JFrame-Class.
> > Best regards, Raffael Vogler
>
> I meant this:
>
> say the dialog has a child component okButton.
>
> To access this button the dialog frame would need to have a method
> similar to this:
>
> JPushButton getOkButton();
>
> This method would have to be public or at least protected.
>
> That way you could use the method as the accessor method to gain access to
> the button.
>
> When you build GUI stuff in JDeveloper I seem to remember that there is no
> easy way of doing the above unless you actually add the code yourself.
>
> Cheers,
>
> dmz17
Received on Fri Feb 28 2003 - 19:54:18 CET