Strange Maximize behavior

Hi,

My app includes a central workingArea and two dockables to the west and south of that working area. However, when I maximize the west or south dockables they only grow to cover the workingArea and not the other dockable. So, for example, if I maximize the dockable to the west then it covers the workingArea but the other dockable to the south is still visible.

The setup code for the layout is a bit complex. I’m trying to integrate DockingFrames into an existing application framework that has its own xml way of describing the layout. However, when I create a very simple case that has the same layout the maximize works fine, so the issue is probably with how I’m setting up the layout. Do you have any insight into what may be causing this?

thanks,

Nick

I have never seen that behavior.

Are you sure that you are using only one WorkingArea and not many nested ones? Are you sure you have only one main-area and not two?

Otherwise I’ve no idea, I can’t help without example.

Thanks! I had another WorkingArea creeping as part of switching “perspectives.”

Hi,

Actually i need such a behavior. If you maximize a dockable located in a CWorkingArea, it shuld be maximized only inside of containing working area.

Hm, short of writing an own action for this there is no solution right now. But I think this is a feature that others might like as well. So I’ll try to rewrite some part of the code such that a) more than one maximize-area is allowed and b) developers can add new maximize-areas.

I’ve nothing to do right now, so maybe this feature is available within the next few hours/days.

Thanks, that would be greate!

Done, uploaded as Preview 6.

I’ve done some testing, but well… the price for this feature is that you are now beta-tester :stuck_out_tongue: (changes are concentrated in one class, so the number of possible failures is somewhat limited)

This new feature (and a small bugfix) is the only change compared to preview 5, so if you get strange errors, just downgrade to p5.

You only need one additional line of code:
workingArea.setMaximizingArea( true );

I might change some things in the background, but as long as you don’t play around with the CStateManager and the MaximizingArea you should not be affected.

[Edit: bug that unintentionally disables the feature repaired…]

I am expressed. I am allready curious to test it:) But unfortunately javaforge is again in devil mode, i can’t access it.

I have to say that this library is really one of the best docking frameworks. Better than the framework is your support, quick and helpful answers.

:mad: Try the archive that is attached to this post. It is not the whole library, just the basics without documentation.

I have to say that this library is really one of the best docking frameworks. Better than the framework is your support, quick and helpful answers.

Thanks. You can help the library be spreading the link :stuck_out_tongue_winking_eye:

Don’t be modest, it is cool whatever you call it!

I upgraded to the preview 6 without any problems, it worked as far like a charm. Thanks again for the new feature again…