On Sun, 16 Feb 2003, Nicola Pero wrote: > > > > Thanks Enrico, I applied your patch ... with some small changes: the > > > correct code was already there, and had been commented out for unknown > > > reasons! > > > > Ok, now it works. But I'd added the second NSPoint "costrP", to permit to > > the divider to draw following the mouse movements; only on mouseUp the > > size of the subviews is set. > > Thanks - yes - I think this is what happens at the moment - the `ghost' > divider follows the mouse movements; on mouseUp the position of the > `ghost' divider becomes the position of the actual `real' divider, and the > size of the subviews is set to that.
In fact, in the Apple documentation, it seems that, if the delegate implements: -splitView:constrainSplitPosition:ofSubviewAt: the divider is drawn at the costrained position. Actually my openstep is broken and I can't verify, but I remember that, on openstep, the divider follows the mouse anyway, beeing costrained only on mouseUp or if the delegate implements -splitView:constrainMinCoordinate:ofSubviewAt: or -splitView:constrainMaxCoordinate:ofSubviewAt: > I'm probably missing your point, if so, please would you explain a bit > more what you'd like to be different, possibly with a small example. :-) > > While looking at this stuff, I noticed that the offset used in the > delegate call was wrong - for example, for a split view with a single > divider, the divider would have offset 1 instead of 0 (as required by the > openstep spec, and as implemented by all other openstep-like systems). I > attempted to fix this ... let me know of any problems. No, no problems, I must only change "1" with "0", or ignore the value, because I've only one divider. _______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gnustep
