[news.eclipse.platform.rcp] Re: nullpointer on the first start of produc

[Ben Brown <ben.brown@xxxxxxxxxx>]

So I think the easy fix that Ricky was refering to was in the same bug 
at comment 67

https://bugs.eclipse.org/bugs/show_bug.cgi?id=67384#c48

doing that will, from the gist that I get, keep the app from crashing, 
it will not make it work though.  In short SWT/AWT doesn't work on the 
mac.  You might be better served by starting a post in the 
eclipse.platform.swt thread.  Somebody over there might have a 
recommendation for some way to get around this.

--Ben

Joachim Schreibmaier wrote:
> hi,
> "Ricky" <ImmortalRick@xxxxxx> wrote:
>
> > There is a easy fix for this. Look at the method new_Frame and you will 
> > see it yourself :)
>
>
> easy fix? Should that mean that I can correct this problem? If there is no 
> way to implement Swing in SWT, why is there the class SWT_AWT in the package 
> org.eclipse.swt.carbon.macosx.ppc_3.1.0.jar?
>
>
> > Within SWT_AWT (org.eclipse.swt.carbon.macosx.ppc_3.1.0.jar)
> >
> > public static Frame new_Frame (final Composite parent) {
> > if (parent == null) SWT.error (SWT.ERROR_NULL_ARGUMENT);
> > if ((parent.getStyle () & SWT.EMBEDDED) == 0) {
> > SWT.error (SWT.ERROR_INVALID_ARGUMENT);
> > }
> > SWT.error (SWT.ERROR_NOT_IMPLEMENTED);
> > return null;
> > }
> >
> > I read this as a no-go for the use of the SWT_AWT bridge on the Mac. There 
> > is a open bug for this 
> > (https://bugs.eclipse.org/bugs/show_bug.cgi?id=67384). Maybe there is a 
> > solution but I simply do not understand what they are talking about.
>
>
> If there is a solution, please post it.