[Kst] View Object UI fixes
Barth Netterfield
netterfield at astro.utoronto.ca
Wed Nov 9 15:46:20 CET 2005
On November 7, 2005 12:13 pm, George Staikos wrote:
> Seems reasonable, but maybe that should be the minimum, as opposed to the
> rule. That way we don't have large dead spots around large objects.
Huh?
>
> > -Make it so that a selected view object, including child items, can be
> > dropped anywhere in the current window.
> > ************ the following suggestion needs discussion ***********
> > -Make it so that on drop, a viewobject will become the child of the
> > highest viewobject which fully contains it (could be the top level view).
> > **************************************************************
>
> Right, it should fall onto the top object it's geometric centre
> intersects.
Lets try "fully contained" first.
> Seems rather straightforward, but we need to be careful not to
> special-case too much. Everything in view objects need to be very generic
> so they're useful from the scripting side and so we can finish implementing
> all the dynamic loading and creation. Once the factories are in place, we
> will be able to dynamically load view objects by name without anything new
> in the loader code, and even have view object plugins.
But the needs of the UI always has to come first.
More information about the Kst
mailing list