rofrol/miglayout

Automatically exported from code.google.com/p/miglayout

miglayout's Issues

[Pull Request] Fixes for JavaDoc

Freshly cloning MigLayout and building miglayout-core, I found that 
mvn install 
wouldn't work properly due to several issues with the JavaDoc.
I am building on JDK 8, maybe some checks are more rigorous there.

I made the required changes to the documentation so the project builds once 
again.

You can pull the changes from 
https://github.com/UrsKR/miglayout/tree/master
if you are interested.

Original issue reported on code.google.com by [email protected] on 13 Apr 2014 at 11:08

Size group shrinks instead of expands

MigPane root = new MigPane(new LC().debug(1000));
root.add(new Label("Label1"), "sgx, wrap");
root.add(new Label("Second Label"), "sgx");

The first label should be expanded to the size of the second label but instead 
the second label is shrunk to the size of the first.

Original issue reported on code.google.com by [email protected] on 12 Apr 2012 at 6:45

JavaFX MigPane doesn't update/sizes correctly

version 4.2
JavaFX8

there are several refresh/repaint problems...

Original issue reported on code.google.com by [email protected] on 6 Nov 2013 at 2:37

Will miglayout support android officially?

The layout managers provided by android is even worse than java's. I hope to 
use miglayout in my android development. For now, I found: 
https://github.com/saynomoo/mig4android , but it is buggy.

Will miglayout support android officially? It will be a great news for android 
developers.

Original issue reported on code.google.com by [email protected] on 23 Sep 2012 at 5:39

Wrong source level in Maven POMs

MigLayout Core uses diamond operators in Grid, but doesn't specify source level 
1.7 in its Maven POM. This leads to errors during the build, as Maven defaults 
to source level 1.6.

I don't provide a pullable commit for this, as I am not sure about your 
intention here - support 1.6 or update?
In any case, you have the necessary configuration in the POM for MigLayout 
JavaFX.

Original issue reported on code.google.com by [email protected] on 17 Apr 2014 at 6:52

The component constraint "eg" throws a "Unknown keyword" exception.

What steps will reproduce the problem?
1. add(mycomponent, "eg");

What is the expected output? What do you see instead?
The white paper explains the expected behavior of the constraint "eg".
I see 
java.lang.IllegalArgumentException: Illegal Constraint: 'eg'
Unknown keyword.


What version of the product are you using? On what operating system?
I downloaded the version on 3-19-2013.

Original issue reported on code.google.com by [email protected] on 26 Feb 2014 at 4:13

MigPane sizing not properly

What steps will reproduce the problem?
Run attached source


What is the expected output? What do you see instead?
MigPane doesn't handle properly the pane sizing, in fact it should match with 
the button's preferred size (like HBox or similar layouts in FX). Instead the 
pane is more little than the button (see screenshot).

What version of the product are you using? On what operating system?
Linux 3.2.0, JRE 1.7.0_45-b18, MigLayout (MigPane) 4.2

Original issue reported on code.google.com by [email protected] on 4 Dec 2013 at 7:01

Attachments:

• FXDemo.java
• FXDemoFixed.java
• HBox_screenshot.png
• MigPane_screenshot.png

Invalid reference in white paper

The MigLayout white paper 
(http://www.migcalendar.com/miglayout/mavensite/docs/whitepaper.html) mentions 
PlatformConverter.getButtonBarOrder(int type) as a reference for detailed tag 
name information. But neither the class, nor the method exists.

Original issue reported on code.google.com by [email protected] on 24 Nov 2012 at 10:08

Loading an image into a button moves adjacent text in latest revision of 5.0-SNAPSHOT

When I load an Image into a Button's ImageView, the layout sees reason to 
change and move adjacent text down, so that it is no longer aligned with the 
button.

Attached is a sample application that illustrates the problem.
Drop the main class in src/test/java, the image into src/test/resources and run 
the main method.

(Sorry for the weird summary, I had no clue how to summarize this issue.)

Original issue reported on code.google.com by [email protected] on 18 Apr 2014 at 7:00

Attachments:

• BorderSolarButton16.png
• Main.java

[RFE] Allow overriding grid gap size between components

It's quite amazing how flexible MigLayout already is, but one thing I find 
missing: I cannot override the layout grid gap size in the component 
constraints!

While I'm already able to achieve the desired layout, it's a bit cumbersome to 
have to define row constraints

new MigLayout("insets dialog", "[grow][][grow][]", "[][][] 1lp");

in order to override the default vertical gap size between two rows.

This also ties the order of components to the definition, which is a potential 
maintenance burden as you have to adjust the row constraints definition if 
components are to be rearranged.

Original issue reported on code.google.com by [email protected] on 28 Nov 2012 at 8:44

TreeView / ListView Conflicts

What steps will reproduce the problem?
1. Create a list view on the left (Or the right, but for me its on the left) in 
a single pane.
2. Create a TreeView on the right side of the pane.
3. At least 20~ items in the listview.
4. 10~ or so leafs with 1-2 children each in the treeview.

What is the expected output? What do you see instead?

Initially (Pre-Interaction) the treeview and listview both remain as they 
should, however after scrolling down some on either and trying to click one of 
the items (On listview or expand a treeview item) the components break and go 
nuts.


What version of the product are you using? On what operating system?

5.0-SNAPSHOT
JDK8u20

Please provide any additional information below.

Initially...

https://i.imgur.com/gYFWMqi.png

And then scrolled down the ListView and than tried to click (Oddly enough also 
the lower items in listView aren't even selectable for some reason) and than 
tried to click a higher item and the listview cut itself in half and became..

https://i.imgur.com/TGJOQDr.png


Messed with the Treeview and than suddenly.. kaboom

https://i.imgur.com/CQF5Vu4.png

Original issue reported on code.google.com by [email protected] on 31 Aug 2014 at 12:38

Most recent 5.0-SNAPSHOT breaks example for Issue #6

The recent changes on 5.0-SNAPSHOT for JavaFX introduce major issues.
Using the latest build renders both my application and the (very simple) 
example[1] I created for Issue #6 unusable.

The commits are 61479b744417 and 96fcdad92c88, but both are so extensive that I 
can't yet pinpoint the issue.

[1]: https://github.com/UrsKR/miglayout-repaint

Original issue reported on code.google.com by [email protected] on 17 Apr 2014 at 7:30

Attachments:

• brokensample.png
• brokenapp.png

Release with debug information

The latest release in Maven central seems to be compiled without debug 
information.

I'd prefer to have them in the official release. Makes it easier to locate any 
bugs/problems with MigLayout.

Original issue reported on code.google.com by [email protected] on 28 Jan 2015 at 9:17

The last stable release is 3 years old…

The last stable release is version 4.2 on 2011/12/09:
http://www.miglayout.com/mavensite/changes-report.html

Release 5.0 is mentioned on the web site but there are only snapshot versions 
without release notes. Most stable projects don't want to use snapshot 
dependencies because they need reproducible builds and don't want to suffer 
from regressions that could be introduced in new snapshots. This means those 
are stuck with release 4.2 for now -- or need to repackage the project.

For example, we are using release 4.2 and just discovered the memory leak 
mentioned here:
http://migcalendar.com/forums/viewtopic.php?f=8&t=3906
which says “This is fixed in the next version out in about a week.” -- this 
was in February 2013…

I know maintaining such a project (for free!) is time consuming but it really 
looks like the project is dying. The only thing that seems to tell the opposite 
is the git activity (which is already good).

I think though that it would be good to already publish version 5.0 and maybe 
continue with small incremental but more frequent versions (e.g. 5.0.1 and so 
on). This would also give more attention to the project and maybe attract some 
contributors. RERO! :)

p.s.: I'm sorry but I could not find a way to contact Mikael directly, neither 
on the web site, nor the forum or here on google code…

Original issue reported on code.google.com by [email protected] on 23 Dec 2014 at 10:33

MigLayout 5.0-SNAPSHOT performs slowly when calculating layout for a lot of nodes in JavaFX 8

Since it resolves issue #6, I migrated my code to MigLayout 5.0-SNAPSHOT.

Running the full application, I took a severe performance hit:
When adding a good number of nodes, part of them stacked MigLayouts to a scene, 
my application spend most of its time calculation the new layout, becoming 
inresponsive for a good while.

My profiler indicates that this is due to the hashcode calculation, where you 
concatenate a number of Strings.

I have attached the profiling results. 

If you need one, I will try to come up with a running example of this issue.

Original issue reported on code.google.com by [email protected] on 12 Apr 2014 at 12:06

Attachments:

• Call_Tree.html
• Hot_Spots.html

Latest 5.0-SNAPSHOT does not render children added via MigPane.getChildren().add(Node)

Testing with the latest SNAPSHOT in the Maven repository, I noticed that nodes 
are rendered in an unexpected fashion - or not rendered at all - when added via 
getChildren.add(Node).

This wouldn't be much of an issue, but direct interaction with the list is the 
only way to inject a node at an earlier position without adressing cells 
directly. Also, direct interaction with the List is the default way of adding 
nodes to a layout in JavaFX.

I assume that this was caused by the changes to constraint-mapping in 
3cf3981af5ec.

Original issue reported on code.google.com by [email protected] on 23 Apr 2014 at 4:22

Attachments:

• MigPaneTest17.java

miglayout-core doesn't work on Android because of missing java.beans classes

...

Original issue reported on code.google.com by [email protected] on 2 Dec 2013 at 3:17

MigPane doesn't seem to honour the 'wrap-text' property of Label

MigPane doesn't seem to honour the 'wrap-text' property of Label. It still 
crops it.

    public void start(Stage stage) throws Exception
    {
        MigPane pane = new MigPane();
        Label label = new Label("Test long label to see if the wrap works ok in a Migpane. I am"
                + " going to have to keep writing because this may not be long enough yet!!");
        pane.setStyle("-fx-border-color:blue");
        label.setWrapText(true);
        pane.getChildren().add(label);
        Scene scene = new Scene(pane, 400, 400);
        stage.setScene(scene);
        stage.show();
    }

I'm assuming it's something to do with the size calculation aspect.

Cheers, 
zonski

Original issue reported on code.google.com by zonski on 9 Jan 2012 at 3:52

Memory Leak in LinkHandler?

We have an application where we are instantiating a lot of (~2000+) instances 
of MigLayout.

For each instance there are created at least one HashMap in LinkHandler. Those 
HashMaps are never cleaned up in our application.

Debugging showed me, that net.miginfocom.layout.LinkHandler#getValue() is never 
called.
I have added some code that calls the read method regularly, which fixes this 
issue. 


BTW:
net.miginfocom.layout.LinkHandler#clearWeakReferencesNow seems to not clear 
VALUES and VALUES_TEMP. 
I don't see any way those collections are cleaned up when 
clearWeakReferencesNow() has been called.

Original issue reported on code.google.com by [email protected] on 28 Jan 2015 at 9:14

Custom component is misaligned in latest revision of 5.0-SNAPSHOT

The latest revision misaligns a custom component in my application.
This is especially visible after initial layout and gets less so after using 
the component.

The screens below show the initial layout and the layout after use.

Note that the component doesn't use MigLayout internally, but there are several 
MigPanes per visible row, as the screenshots taken with Debug activated 
illustrate.

I haven't yet tried to create a running sample of this issue, will do on 
request.

Original issue reported on code.google.com by [email protected] on 18 Apr 2014 at 7:54

Attachments:

• Initial.PNG
• InitialWithDebug..PNG
• AfterUse.PNG
• AfterUseWithDebug.PNG

MigLayout class is final

I'm using the last stable Miglayout 4.0 and got a Problem, that my Containers 
in the layout could maximal be 32767 pixels wide.

The problem was found soon in the following method:
public Dimension maximumLayoutSize(Container parent)
{
   return new Dimension(Short.MAX_VALUE, Short.MAX_VALUE);
}


the problem now is, i can't create a new class to overwrite the methode, 
because the MigLayout class is final.
Please don't do that.

Regards

Original issue reported on code.google.com by [email protected] on 21 Jan 2015 at 4:24