[sip-comm-dev] NPE in UIServiceImpl


#1

Lubo,

the UIServiceImpl throws a NPE right during initialization:

...
     public void loadApplicationGui()
     {
         this.setDefaultThemePack();

         this.mainFrame = new MainFrame();
...

Thus "mainFrame" is set only after setDefaultThemePack(). During
setDefaultThemePack() the function initCustomFonts() is call which
in turn accesses "mainFrame" -> NPE.

Would it do any harm to first set "mainFrame" before calling
setDefaultThemePack()? Or is it necessary to look at initCustomFonts()?

Regards,
Werner

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Hi Werner,

Thank you!

I believe r4849 remedies the NPE. I hope I'm not stepping on Yana's
toes with the fix.

Best regards,
Lubo

···

On Sun, Dec 14, 2008 at 3:56 PM, Werner Dittmann <Werner.Dittmann@t-online.de> wrote:

Lubo,

the UIServiceImpl throws a NPE right during initialization:

...
   public void loadApplicationGui()
   {
       this.setDefaultThemePack();

       this.mainFrame = new MainFrame();
...

Thus "mainFrame" is set only after setDefaultThemePack(). During
setDefaultThemePack() the function initCustomFonts() is call which
in turn accesses "mainFrame" -> NPE.

Would it do any harm to first set "mainFrame" before calling
setDefaultThemePack()? Or is it necessary to look at initCustomFonts()?

Regards,
Werner

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net