Niclas, Ok, though as I think it out, I think a slight API change might make SplitPane more usable to callers. What if splitLocation were a float value that represented the percentage split instead an absolute value? Then, as the user dragged the splitter, the skin would update the percentage. And you as the caller could specify the percentage just how you'd like. For your use case, do you need to serialize the absolute values of the split location, or if split pane were changed in this way, could you serialize the percentages and then re-use them when you brought back up the UI?
-T On Tue, Aug 4, 2009 at 9:08 AM, Niclas Hedhman <[email protected]> wrote: > Todd, > Perhaps it is not an issue at all, since I realize that once I get further > down the road, the split settings must be saved across starts, and a > programmatic approach is need. > > I hope I will manage to get the base of the app up and running in full by > this week, and sure will have more feedback by then. > > -- Niclas >
