- This topic has 9 replies, 5 voices, and was last updated 16 years, 11 months ago by Riyad Kalla.
-
AuthorPosts
-
paulmolMember1 I have a form consisting of mutiply JPanels put vertically
When I move some panels up or down they have tendency
to suddenly expand horizontaly to a very large size, several times larger than my screen.Is this a bug or a feature?
2. within each panel, when I move elements ( e.g JTextFields) they sometimes
cause other elements to change size or location in unpredicatable way.Same applies by the way to a movement of one JPanel affecting other JPanels.
Is there any way to tell Matisse “just move this element, don’t touch
any other elements ?”
and “move this element where I put it, don’t snap to any grid etc ”Paul
Riyad KallaMemberPaul,
It depends entirely on the layout manager you are using. If you are using the default layout manager (the one that allows you to snap your elements to guides) then no unfortunately this is the expected behavior. That particular layout manager works off of references to sides of containers, other components, anchors and height/width rules… so you cannot just freely move things around.. they are effected by, and related to every other component around them.If you just want to layout components completely freely, set the layout manager for the container you are laying out to Null Layout, that lets you drag things around and absolutely position them at x/y coordinates and with specific sizes.
paulmolMemberRiyad,
Thank you for answer.I wanted to use the default manager.
I wish someone described it’s rules and alghoritms one day so we would
know when acts as expected and when it is a bug.Working with it for several weeks with many forms I can say a lot of positioning it is doing does not make any sense.
Good that at least “undo” works most of the time.
-Paul
Riyad KallaMemberPaul,
It’s definately one of those layout managers you learn to work with, but when you do, it’s so frigging fantastic it’s hard to stay mad at it 😉
dip jahidMemberThis message has not been recovered.
Riyad KallaMemberThis message has not been recovered.
GregMemberJust wanted to post a quick note that we have indeed fixed this in the 6.0.1 development stream.
Douglas M HurstParticipantThis message has not been recovered.
Douglas M HurstParticipantThis message has not been recovered.
Riyad KallaMemberThis message has not been recovered.
-
AuthorPosts