Skip to content
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

The swing application does not always update when view properties are changed #7

Open
scharf opened this issue Feb 16, 2017 · 7 comments

Comments

@scharf
Copy link

scharf commented Feb 16, 2017

In the JavaFX version of the app, setting properties immediately changes the UI. In the Swing app this is not the always case.

For example in the Layouts -> Border, you have to resize the window in order to see changes to the margins or the gaps.

@rjahn
Copy link
Member

rjahn commented Feb 16, 2017

This is a JVx Swing UI problem. Has nothing to do with kitchensink. Please open a JVx ticket :)

@RobertZenz
Copy link
Collaborator

To expand a little bit on that, the Kitchensink is really just a very "thin" demo application built with JVx. If the Kitchensink behaves differently on different technologies, there is a very good possibility that this is a mismatch in JVx itself (actually, I can't come up with a different explanation) so should be reported on the JVx ticket system.

I can create this ticket tomorrow if you do not wish to register at the ticket system and create the ticket. Though, I'd welcome you to do it, especially if you plan to look further into JVx.

@scharf
Copy link
Author

scharf commented Feb 16, 2017

@scharf
Copy link
Author

scharf commented Feb 16, 2017

I understand the Kitchensink is a demo application, however it reveals a lot of problems with JVX.

I wonder if there is another JVX application that is used to demonstrate the expected behaviour of all UI elements?

What is the best way to proceed here? I found a lot of other small and big usability problems, inconsistencies between Swing and JavaFX. Where should I report them?

I am not sure if it makes sense to create a new issuer for each problem here or in the JVx ticket system, because I assume that most of the bugs are known and triaging the buts may be unnecessary extra effort on your side....

Should I create a single document with the problems I found?

@rjahn
Copy link
Member

rjahn commented Feb 17, 2017

The most important thing here is that you report the bug. If you feel comfortable with a document, no problem.

Sure, one ticket per problem will be fine for us!

@RobertZenz
Copy link
Collaborator

RobertZenz commented Feb 17, 2017

Please note that we do have a separate project for JVxFX. So if you report discrepancies between Swing and JavaFX, you should report them in the JVxFX project.

@rjahn
Copy link
Member

rjahn commented Feb 27, 2017

Any news here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants