On Wed, 15 Oct 2025 22:01:45 GMT, Andy Goryachev <[email protected]> wrote:
>> I think I see what you are getting at now. Let's take a step back. >> >> What we want is to give the app developer enough information to know what >> the purpose of calling this method is, and what the effect will be. What we >> don't want to do is say _how_ that is done. So you are right that we >> shouldn't appeal to VirtualFlow since it isn't really relevant in this >> context. Likewise, we don't want to constrain it with implementation details. >> >> The `refresh()` method was added by >> [JDK-8098085](https://bugs.openjdk.org/browse/JDK-8098085) to allow an app >> developer with a custom cell to say, in effect, "even if it doesn't look >> like anything is changed, get the contents of the cells anyway". If that's >> what `updateItem()` does, then yes we can say that. Otherwise, we need to >> find some other way to say it. > > exactly, thank you @kevinrushforth Discussed with Kevin yesterday, what do you think of this version: * Calling {@code refresh()} forces the XXX to update what it is showing to * the user. This is useful in cases where the underlying data source has * changed in a way that is not observed by the XXX itself. ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/1830#discussion_r2441415948
