Hi Janak,
We are still using ULC 6.0.4 but are in the process to port our ULC
extensions to ULC 6.1. So in the near future - probably two weeks from now -
we'll be on ULC 6.1.
Our scrollpane doesn't really scroll the viewport. The viewport communicates
the current scroll position to the table, which implements the
getCellRect(), columnAtPoint() and rowAtPoint() according to the
scrollpositions and to which columns and rows are fixed. The UI delegate
first paints the movable part of the table and then - on top of it - the
fixed parts.
The cells that start at a negative x coordinate sometimes aren't fetched.
There is a turning point where the cell still starts at a negative
x-coordinate (-83 or something like that) when ULC suddenly fetches that
cell.
Cheers,
Robert
----- Original Message -----
From: "Janak Mulani" <[EMAIL PROTECTED]>
To: "ulc rbeeger" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, June 01, 2006 5:24 PM
Subject: RE: [ULC-developer] How do ULCTable and ULCTreeTable decide which
cells to update from server
Hi Robert,
Which version of ULC are you using?
You say that you have extended ULCScrollPane and ULCTable with their
client
side proxies.
ULC's lazy loading mechanism relies on some conditions in exactly these
widgets.
Could you please tell us what exactly your extensions are doing and how
have
you implemented them?
Also, you say that some cells are fetched and some are not. Could you tell
which ones are fetched and which ones not?
Thanks and regards,
Janak
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of ulc rbeeger
Sent: Thursday, June 01, 2006 2:06 PM
To: [EMAIL PROTECTED]
Subject: [ULC-developer] How do ULCTable and ULCTreeTable decide which
cells
to update from server
Hi!
We have very specialized table and treetable widgets with matching ULC
extensions.One of the special features is that they display fixed columns
at
the left side of the table and fixed rows at the bottom of it.
To achieve this we have developed a new viewport, a new scrollpane and a
new
table.
When we trigger a row update the following happens (or seems to happen):
1. The client side cached data for the row is deleted. All cells now
contain
a null value.
2. The new values for some cells are fetched from the server.
Now the problem is that ULC doesn't fetch the values for all visible
cells.
How does ULC decide what cells are visible? Our widget works under Swing.
Swing asks for the values of all visible cells. There must be some
difference between what Swing recognizes as visible and what ULC guesses
to
be needed.
Cheers,
Robert
_______________________________________________
ULC-developer mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/ulc-developer
_______________________________________________
ULC-developer mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/ulc-developer
