Hi Paul,
I wrote about this problem in the past but receive no ack, I was feeling
alone...
I have an ugly patch that at least prevent the NPE and keep the workspace in
working condition. I tried to dig further in the debugger but the eclipse UI
code is really hard to follow.
You can apply my patch on your source. It may be added to the project by a
commiter if it is acceptable.
In the file
wolips/core/plugins/org.objectstyle.wolips.componenteditor/java/org/objectstyle/wolips/componenteditor/part/HtmlWodTab.java
beginning at line 223 you should have:
if (sashWeights.length == getParentSashForm().getWeights().length) {
getParentSashForm().setWeights(sashWeights);
}
Replace them with these:
if (sashWeights.length == getParentSashForm().getWeights().length) {
if (sashWeights[1] / (float)sashWeights[0] < 0.15) {
sashWeights[0] = 85;
sashWeights[1] = 15;
}
getParentSashForm().setWeights(sashWeights);
}
This patch ensure the WOD pane is at least 15% of the editor height. I figured
this amount by trying different values with different windows size; it should
be safe.
I spend fer hour figuring out this but never found how to fix the real problem.
Samuel
Le 2014-10-21 à 03:16, Paul Hoadley <pa...@logicsquad.net> a écrit :
> On 21 Oct 2014, at 5:22 pm, Andre Palubitzki <an...@palubitzki.de> wrote:
>
>> You can prevent this NPE when you never (!) resize the pane of the component
>> editor. I’m using Luna and WOLips since quite some time and I can use the WO
>> component editor with no further problems.
>> To remove this error when you accidentally have triggered it thru resizing
>> you only have to remove the file „<workspace
>> directory>/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.objectstyle.wolips.wodclipse.core.prefs“
>> (as some time someone else mentioned) and restart Eclipse.
>>
>> Hope this helps!
>
> It sure does, Andre. Thanks a lot.
>
> This remains something of a show-stopper for me though, as I use inline
> bindings almost exclusively, but WOLips now insists on using half that tab to
> display the empty WOD. Moving the divider is fine for the tab currently
> displayed, but then triggers the original bugs for any future tabs.
>
> Anyway, I see now that this was discussed back in February, including a
> discussion of funding someone to fix this, but the thread trails off. Can we
> resurrect that idea? Is there _anyone_ still subscribed to this list that
> could do the work? We would also be willing to contribute to such a project,
> but it's not even clear there's anyone left that could do the work, let alone
> whether there's a coherent list of things that need fixing beyond the ageing
> list at https://github.com/wocommunity/wolips/issues.
>
>
> --
> Paul Hoadley
> http://logicsquad.net/
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/samuel%40samkar.com
>
> This email sent to sam...@samkar.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
