Closed FelixBaensch closed 5 months ago
The enum values (or their text representations) should then also be used in the GUI classes that define the cell value properties, right? Are these displayed and hence language-specific?
The enum values (or their text representations) should then also be used in the GUI classes that define the cell value properties, right?
Done
Are these displayed and hence language-specific?
No, they are not
Thank you, looks much better now! I'm just still hung up on this:
How about defining ascending/descending via a bool? This way, no JavaFx class would be used in this model class. Or can there be other sort orders, hypothetically?
And the TableColumn.SortType enum appears to only have the two values ascending and descending anyway.
Thank you, looks much better now! I'm just still hung up on this:
How about defining ascending/descending via a bool? This way, no JavaFx class would be used in this model class. Or can there be other sort orders, hypothetically?
And the TableColumn.SortType enum appears to only have the two values ascending and descending anyway.
Unfortunately I overlooked that. That would require a method to parse the TableColumn.SortType into a Boolean. I would rather argue in favor of moving the CollectionUtils to a controller package if you want to avoid the fx class in the model area.
That would require a method to parse the TableColumn.SortType into a Boolean.
It wouldn't be that complicated, would it? I'd name the boolean parameter "ascending" and the method call would be like "tmpSortType.equals(ASCENDING)". If false, the used order is descending. Am I missing something?
If it makes you happy
If it makes you happy
It does 🤗
Issues
2 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
Do you want to merge this or should I?
How about defining ascending/descending via a bool? This way, no JavaFx class would be used in this model class. Or can there be other sort orders, hypothetically?