[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-openjfx-dev
Subject:    Re: Virtual Flow enhancements
From:       Johan Vos <johan.vos () gluonhq ! com>
Date:       2022-09-15 19:20:32
Message-ID: CABxFH2ECP6Zxwb1NEX7C6mFhD-wJ4WTPqPQqE5aXwo9-h_MMZQ () mail ! gmail ! com
[Download RAW message or body]

On Wed, Sep 14, 2022 at 12:19 PM Dirk Lemmermann <dlemmermann@gmail.com>
wrote:

> Hi,
>
>
> FlexGanttFX used to make this work via bidirectional bindings of the
> properties of the vertical scrollbars of both VirtualFlows. With the latest
> fixes to the VirtualFlow the assumption that two identically populated
> VirtualFlows would provide identical values to the ScrollBar properties is
> no longer true. The attempt to bind the "position" property also failed and
> a work-around that Johan provided also has not been successful, yet (a
> customer of mine is still evaluating it).
>

I don't know what work-around you refer to, but I often point to public
methods in VirtualFlow that, when properly combined, allow many usecases. I
sometimes see code where the information about the positioning of elements
in the VirtualFlow is obtained via the position of the scrollbar thumb,
which seems a really odd way to get this info (and especially unreliable as
the relation with the real positioning of cells is unspecified). There are
other methods on VirtualFlow that imho are better suited for
getting/setting information.
What I want to avoid is that we have 2 API's that almost achieve the same.
Hence, before considering a new method or property, I think we should make
sure that there is currently no existing (documented) way to achieve it. I
am pretty sure there are cases that can not be solved with the existing set
of API's, and those cases are exactly what I'm looking for.

- Johan

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Wed, Sep 14, 2022 at 12:19 PM Dirk Lemmermann &lt;<a \
href="mailto:dlemmermann@gmail.com">dlemmermann@gmail.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br><br> <br>
FlexGanttFX used to make this work via bidirectional bindings of the properties of \
the vertical scrollbars of both VirtualFlows. With the latest fixes to the \
VirtualFlow the assumption that two identically populated VirtualFlows would provide \
identical values to the ScrollBar properties is no longer true. The attempt to bind \
the "position" property also failed and a work-around that Johan provided also has \
not been successful, yet (a customer of mine is still evaluating \
it).<br></blockquote><div><br></div><div>I don&#39;t know what work-around you refer \
to, but I often point to public methods in VirtualFlow that, when properly combined, \
allow many  usecases. I sometimes see code where the information about the \
positioning of elements in the VirtualFlow is obtained via the position of the \
scrollbar thumb, which seems a really odd way to get this info (and especially \
unreliable as the relation with the real positioning of cells is unspecified). There \
are other methods on VirtualFlow that imho are better suited for getting/setting \
information.  </div><div>What I want to avoid is that we have 2 API&#39;s that almost \
achieve the same. Hence, before considering a new method or property, I think we \
should make sure that there is currently no existing (documented) way to achieve it. \
I am pretty sure there are cases that can not be solved with the existing set of \
API&#39;s, and those cases are exactly what I&#39;m looking \
for.<br></div><div><br></div><div>- \
Johan</div><div><br></div><div><br></div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]