Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / dooApp/FXForm2 issues and pull requests
#163 - Allow class constraint in custom FXML skin
Issue -
State: closed - Opened by kevinsdooapp almost 7 years ago
Labels: feature
#163 - Allow class constraint in custom FXML skin
Issue -
State: closed - Opened by kevinsdooapp almost 7 years ago
Labels: feature
#162 - Constraint validation error when passing from a valid value to an invalid value to previous valid value
Issue -
State: closed - Opened by fblan about 7 years ago
- 1 comment
Labels: bug
#162 - Constraint validation error when passing from a valid value to an invalid value to previous valid value
Issue -
State: closed - Opened by fblan about 7 years ago
- 1 comment
Labels: bug
#162 - Constraint validation error when passing from a valid value to an invalid value to previous valid value
Issue -
State: closed - Opened by fblan about 7 years ago
- 1 comment
Labels: bug
#162 - Constraint validation error when passing from a valid value to an invalid value to previous valid value
Issue -
State: closed - Opened by fblan about 7 years ago
- 1 comment
Labels: bug
#161 - The FXFormNode could never be initialized
Pull Request -
State: closed - Opened by Rizen59 about 7 years ago
Labels: bug
#160 - Fix potential memory leak in DefaultAdapterProvider
Pull Request -
State: closed - Opened by Rizen59 about 7 years ago
Labels: bug
#159 - Issue #158 : Add a choicebox node which ask a user confirmation befor…
Pull Request -
State: closed - Opened by kevinsdooapp about 7 years ago
- 1 comment
#159 - Issue #158 : Add a choicebox node which ask a user confirmation befor…
Pull Request -
State: closed - Opened by kevinsdooapp about 7 years ago
- 1 comment
#158 - Add a choicebox node which ask a user confirmation before updating the bean property
Issue -
State: closed - Opened by kevinsdooapp about 7 years ago
Labels: feature
#158 - Add a choicebox node which ask a user confirmation before updating the bean property
Issue -
State: closed - Opened by kevinsdooapp about 7 years ago
Labels: feature
#158 - Add a choicebox node which ask a user confirmation before updating the bean property
Issue -
State: closed - Opened by kevinsdooapp about 7 years ago
Labels: feature
#157 - Add an auto complete address field factory
Issue -
State: closed - Opened by amischler over 7 years ago
- 2 comments
Labels: improvement
#157 - Add an auto complete address field factory
Issue -
State: closed - Opened by amischler over 7 years ago
- 2 comments
Labels: improvement
#157 - Add an auto complete address field factory
Issue -
State: closed - Opened by amischler over 7 years ago
- 2 comments
Labels: improvement
#157 - Add an auto complete address field factory
Issue -
State: closed - Opened by amischler over 7 years ago
- 2 comments
Labels: improvement
#156 - Fix StackOverflowException when loading bean with no-property fields due to #154
Pull Request -
State: closed - Opened by Rizen59 over 7 years ago
Labels: bug
#156 - Fix StackOverflowException when loading bean with no-property fields due to #154
Pull Request -
State: closed - Opened by Rizen59 over 7 years ago
Labels: bug
#156 - Fix StackOverflowException when loading bean with no-property fields due to #154
Pull Request -
State: closed - Opened by Rizen59 over 7 years ago
Labels: bug
#156 - Fix StackOverflowException when loading bean with no-property fields due to #154
Pull Request -
State: closed - Opened by Rizen59 over 7 years ago
Labels: bug
#155 - Unexpected behavior when managing multiple sources with empty ListProperty #154
Pull Request -
State: closed - Opened by Rizen59 over 7 years ago
Labels: bug
#155 - Unexpected behavior when managing multiple sources with empty ListProperty #154
Pull Request -
State: closed - Opened by Rizen59 over 7 years ago
Labels: bug
#155 - Unexpected behavior when managing multiple sources with empty ListProperty #154
Pull Request -
State: closed - Opened by Rizen59 over 7 years ago
Labels: bug
#154 - Managing multiple source with empty ListProperty
Issue -
State: closed - Opened by Rizen59 over 7 years ago
Labels: bug
#154 - Managing multiple source with empty ListProperty
Issue -
State: closed - Opened by Rizen59 over 7 years ago
Labels: bug
#154 - Managing multiple source with empty ListProperty
Issue -
State: closed - Opened by Rizen59 over 7 years ago
Labels: bug
#154 - Managing multiple source with empty ListProperty
Issue -
State: closed - Opened by Rizen59 over 7 years ago
Labels: bug
#153 - Java 9 compatibility
Issue -
State: closed - Opened by amischler over 7 years ago
- 1 comment
Labels: improvement
#153 - Java 9 compatibility
Issue -
State: closed - Opened by amischler over 7 years ago
- 1 comment
Labels: improvement
#153 - Java 9 compatibility
Issue -
State: closed - Opened by amischler over 7 years ago
- 1 comment
Labels: improvement
#152 - The default uncaught exception handler should be restored when modified in a test
Issue -
State: closed - Opened by amischler over 7 years ago
- 1 comment
Labels: technical task
#152 - The default uncaught exception handler should be restored when modified in a test
Issue -
State: closed - Opened by amischler over 7 years ago
- 1 comment
Labels: technical task
#152 - The default uncaught exception handler should be restored when modified in a test
Issue -
State: closed - Opened by amischler over 7 years ago
- 1 comment
Labels: technical task
#152 - The default uncaught exception handler should be restored when modified in a test
Issue -
State: closed - Opened by amischler over 7 years ago
- 1 comment
Labels: technical task
#151 - ArrayIndexOutOfBoundsException in ClassLevelValidator
Issue -
State: closed - Opened by amischler over 7 years ago
- 2 comments
Labels: bug
#151 - ArrayIndexOutOfBoundsException in ClassLevelValidator
Issue -
State: closed - Opened by amischler over 7 years ago
- 2 comments
Labels: bug
#151 - ArrayIndexOutOfBoundsException in ClassLevelValidator
Issue -
State: closed - Opened by amischler over 7 years ago
- 2 comments
Labels: bug
#150 - IllegalStateException in ClassLevelValidator
Issue -
State: closed - Opened by amischler over 7 years ago
- 2 comments
Labels: bug
#150 - IllegalStateException in ClassLevelValidator
Issue -
State: closed - Opened by amischler over 7 years ago
- 2 comments
Labels: bug
#150 - IllegalStateException in ClassLevelValidator
Issue -
State: closed - Opened by amischler over 7 years ago
- 2 comments
Labels: bug
#150 - IllegalStateException in ClassLevelValidator
Issue -
State: closed - Opened by amischler over 7 years ago
- 2 comments
Labels: bug
#149 - Class level constraints in group Warning are not being validated
Issue -
State: closed - Opened by amischler over 7 years ago
- 2 comments
Labels: bug
#149 - Class level constraints in group Warning are not being validated
Issue -
State: closed - Opened by amischler over 7 years ago
- 2 comments
Labels: bug
#149 - Class level constraints in group Warning are not being validated
Issue -
State: closed - Opened by amischler over 7 years ago
- 2 comments
Labels: bug
#149 - Class level constraints in group Warning are not being validated
Issue -
State: closed - Opened by amischler over 7 years ago
- 2 comments
Labels: bug
#148 - Added a unit test for issue #131
Pull Request -
State: closed - Opened by xylo over 7 years ago
#148 - Added a unit test for issue #131
Pull Request -
State: closed - Opened by xylo over 7 years ago
#148 - Added a unit test for issue #131
Pull Request -
State: closed - Opened by xylo over 7 years ago
#148 - Added a unit test for issue #131
Pull Request -
State: closed - Opened by xylo over 7 years ago
#147 - Add custom factory provided for UUID class
Issue -
State: closed - Opened by ouaibsky over 7 years ago
- 2 comments
#147 - Add custom factory provided for UUID class
Issue -
State: closed - Opened by ouaibsky over 7 years ago
- 2 comments
#147 - Add custom factory provided for UUID class
Issue -
State: closed - Opened by ouaibsky over 7 years ago
- 2 comments
#146 - How to get rid of the "No adapter between types ... found" warnings?
Issue -
State: closed - Opened by xylo over 7 years ago
- 2 comments
#146 - How to get rid of the "No adapter between types ... found" warnings?
Issue -
State: closed - Opened by xylo over 7 years ago
- 2 comments
#146 - How to get rid of the "No adapter between types ... found" warnings?
Issue -
State: closed - Opened by xylo over 7 years ago
- 2 comments
#146 - How to get rid of the "No adapter between types ... found" warnings?
Issue -
State: closed - Opened by xylo over 7 years ago
- 2 comments
#145 - DefaultResourceProvider bundle property is not bound to the Form ress…
Pull Request -
State: closed - Opened by amischler over 7 years ago
#145 - DefaultResourceProvider bundle property is not bound to the Form ress…
Pull Request -
State: closed - Opened by amischler over 7 years ago
#145 - DefaultResourceProvider bundle property is not bound to the Form ress…
Pull Request -
State: closed - Opened by amischler over 7 years ago
#144 - DefaultResourceProvider bundle property is not bound to the Form ressourceBundle property
Issue -
State: closed - Opened by amischler over 7 years ago
- 1 comment
Labels: bug
#144 - DefaultResourceProvider bundle property is not bound to the Form ressourceBundle property
Issue -
State: closed - Opened by amischler over 7 years ago
- 1 comment
Labels: bug
#144 - DefaultResourceProvider bundle property is not bound to the Form ressourceBundle property
Issue -
State: closed - Opened by amischler over 7 years ago
- 1 comment
Labels: bug
#143 - Fix for issue #142
Pull Request -
State: closed - Opened by kevinsdooapp over 7 years ago
#143 - Fix for issue #142
Pull Request -
State: closed - Opened by kevinsdooapp over 7 years ago
#143 - Fix for issue #142
Pull Request -
State: closed - Opened by kevinsdooapp over 7 years ago
#143 - Fix for issue #142
Pull Request -
State: closed - Opened by kevinsdooapp over 7 years ago
#142 - When switching very fast the source of form with FXML skin, a wrong property might be edited
Issue -
State: closed - Opened by kevinsdooapp over 7 years ago
- 1 comment
Labels: bug
#142 - When switching very fast the source of form with FXML skin, a wrong property might be edited
Issue -
State: closed - Opened by kevinsdooapp over 7 years ago
- 1 comment
Labels: bug
#142 - When switching very fast the source of form with FXML skin, a wrong property might be edited
Issue -
State: closed - Opened by kevinsdooapp over 7 years ago
- 1 comment
Labels: bug
#142 - When switching very fast the source of form with FXML skin, a wrong property might be edited
Issue -
State: closed - Opened by kevinsdooapp over 7 years ago
- 1 comment
Labels: bug
#141 - BufferedElementFactoryTest failing randomly
Issue -
State: closed - Opened by amischler almost 8 years ago
- 1 comment
Labels: bug
#141 - BufferedElementFactoryTest failing randomly
Issue -
State: closed - Opened by amischler almost 8 years ago
- 1 comment
Labels: bug
#141 - BufferedElementFactoryTest failing randomly
Issue -
State: closed - Opened by amischler almost 8 years ago
- 1 comment
Labels: bug
#141 - BufferedElementFactoryTest failing randomly
Issue -
State: closed - Opened by amischler almost 8 years ago
- 1 comment
Labels: bug
#140 - How to add a custom validator if a certain annotation is present
Issue -
State: closed - Opened by xylo almost 8 years ago
- 2 comments
#140 - How to add a custom validator if a certain annotation is present
Issue -
State: closed - Opened by xylo almost 8 years ago
- 2 comments
#140 - How to add a custom validator if a certain annotation is present
Issue -
State: closed - Opened by xylo almost 8 years ago
- 2 comments
#140 - How to add a custom validator if a certain annotation is present
Issue -
State: closed - Opened by xylo almost 8 years ago
- 2 comments
#139 - implemented issue #138 (Allow to set custom ResourceProvider)
Pull Request -
State: closed - Opened by xylo almost 8 years ago
- 2 comments
#139 - implemented issue #138 (Allow to set custom ResourceProvider)
Pull Request -
State: closed - Opened by xylo almost 8 years ago
- 2 comments
#139 - implemented issue #138 (Allow to set custom ResourceProvider)
Pull Request -
State: closed - Opened by xylo almost 8 years ago
- 2 comments
#139 - implemented issue #138 (Allow to set custom ResourceProvider)
Pull Request -
State: closed - Opened by xylo almost 8 years ago
- 2 comments
#138 - Allow to set custom ResourceProvider
Issue -
State: closed - Opened by xylo almost 8 years ago
- 3 comments
Labels: improvement
#138 - Allow to set custom ResourceProvider
Issue -
State: closed - Opened by xylo almost 8 years ago
- 3 comments
Labels: improvement
#138 - Allow to set custom ResourceProvider
Issue -
State: closed - Opened by xylo almost 8 years ago
- 3 comments
Labels: improvement
#138 - Allow to set custom ResourceProvider
Issue -
State: closed - Opened by xylo almost 8 years ago
- 3 comments
Labels: improvement
#137 - When switching very fast the source of the form between two sources i…
Pull Request -
State: closed - Opened by amischler almost 8 years ago
#137 - When switching very fast the source of the form between two sources i…
Pull Request -
State: closed - Opened by amischler almost 8 years ago
#136 - When switching very fast the source of the form between two sources i…
Pull Request -
State: closed - Opened by amischler almost 8 years ago
Labels: bug
#136 - When switching very fast the source of the form between two sources i…
Pull Request -
State: closed - Opened by amischler almost 8 years ago
Labels: bug
#136 - When switching very fast the source of the form between two sources i…
Pull Request -
State: closed - Opened by amischler almost 8 years ago
Labels: bug
#135 - When switching very fast the source of the form between two sources in a background thread, a wrong property might be edited
Issue -
State: closed - Opened by amischler almost 8 years ago
- 1 comment
Labels: bug
#135 - When switching very fast the source of the form between two sources in a background thread, a wrong property might be edited
Issue -
State: closed - Opened by amischler almost 8 years ago
- 1 comment
Labels: bug
#135 - When switching very fast the source of the form between two sources in a background thread, a wrong property might be edited
Issue -
State: closed - Opened by amischler almost 8 years ago
- 1 comment
Labels: bug
#135 - When switching very fast the source of the form between two sources in a background thread, a wrong property might be edited
Issue -
State: closed - Opened by amischler almost 8 years ago
- 1 comment
Labels: bug
#134 - implemented issue #104 (buffering of form values)
Pull Request -
State: closed - Opened by xylo almost 8 years ago
- 8 comments
#134 - implemented issue #104 (buffering of form values)
Pull Request -
State: closed - Opened by xylo almost 8 years ago
- 8 comments
#134 - implemented issue #104 (buffering of form values)
Pull Request -
State: closed - Opened by xylo almost 8 years ago
- 8 comments
#134 - implemented issue #104 (buffering of form values)
Pull Request -
State: closed - Opened by xylo almost 8 years ago
- 8 comments