"Mikael Svane" <
[hidden email]> wrote in message
news:bvmlm2$u7utd$
[hidden email]...
> If the cursor is moved above a Splitter, Splitter>>onGetCursor: is
> evaluated. This causes Splitter>>cursor to evaluate, which sends
#isVertical
> to self. Splitter>>isVertical looks like this:
>
> ^self parentView layoutManager isVertical
>
> This, however, only works when the parentView uses instances of
> ProportionalLayout as it's layout manager. No other layout manager has an
> #isVertical method and moving the cursor above the splitter then causes a
> walkback (in my case "FramingLayout does not understand #isVertical").
This
> is also a problem in the cases where there is no layoutManager in the
parent
> view. I suppose that this is a bug.
It is by design, as explained in the class comment of Splitter: "Normally, a
Splitter requires that the parent view in which it is placed is under the
control of a ProprtionalLayout manager."
It is possible that a Splitter could be made to work with some other
LayoutManagers, such as FramingLayout, or a custom layout manager, but it is
only intended for use in a parent that has a proportional layout.
Regards
Blair