-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migpane problem with size #77
Comments
That is very strange. The only thing I can come to think of is if the textfields are reporting different preferred or maximum sizes. Also, does anything change if the windows are resized (which means the layout will be recalculated)? Other than that it's hard for me to solve it if it is local to just one computer. Chances are that there's something strange with that computer rather than with MigLayout, but stranger things have happened. :) |
Hi, Have not rolled out our JavaFX software yet so this might not be isolated problem. Have not seen this problem with swing miglayout on 200 + computers. Any more ideas? UPDATED. resize the windows did not do anything. still bad. Computer 1 (bad) Computer 2. |
I JavaFX running with MigLayout on multiple computers at customers and a lot of on Windows, so I don't think this is a general problem. MigLayout also have quite a large user base, so it it was a generic problem I think I would have heard about it, or at least I hope so. :) |
Strange that this same computer Mig works fine with swing but not JavaFX. Same Java version. |
It is strange indeed. |
Hello, If you want we can give you access to this laptop or provide you with debug information. Please address this issue of your great library. Thanks. |
Hello,
Having used Mig for Swing for many and now am transitioning to JavaFX and have discovered a strange issue how nodes are displayed on differnet computers.
Consider this code;
`public class MigPaneMain extends Application {
}`
Both computer Windows 10. Java-8_181. MipPane. 5.3.
Computer 1. w 200! is not respected
Computer 2
Let me know if you need debug information.
Br,
Hugo
The text was updated successfully, but these errors were encountered: