-
FEATURED COMPONENTS
First time here? Check out the FAQ!
Just to know if is just me (using zkgrails), or anyone else having some glitches with the two most exciting featues on ZK 5.0.2
Autopaging is totaly crazy.
1. it didn't calculated correctly, because always (really always) there is a scroll with about 30 px (I'm guessing that this is another glitch with borderlayout... will see this later)
2. I saw a case where it had a list with 25 elements. Page 1: 1 to 13, Page 2: 16 to 25. I think ZK somehow knows that item 14 and 15 are not important and decided not to show to the user =]
3. The most agitated one. It gone to a loop and kept adding and then removing the itens, constantly.
Renderdefer works most of the time. But I got a case where I defer a panel creation, and hit an JS exception:
Canno read property 'style' of undefined zk.wpd:12076
Again, I might be hitting this issues because I'm using zkgrails, and ZK itself is flawless. Just to see if an ZK user has this issues.
Kind regards,
Madruga
Hi Madruga,
i must wait until it's in the maven repo. But i'm very interested in this features.
And i'm at the same line as you that's the most exciting feature.
Can you catch the getMaxRows() ?? (Don't know the exact methodName) in an onCreate$myWindow() event for passing it to your Service/DAO method ???
best
Stephan
@madruga0315
https://sourceforge.net/tracker/?func=detail&aid=3002530&group_id=152762&atid=785191
It's serious, I posted it to bug tracking.
Can you provide us more info and sample code to reproduce the issue?
Sincerely,
Peter
@Stephan
I don't think so. The getPageSize() is ignored when using autopaging, so it just returns 20 (the default value). I guess that this calculations are done after the model has been assigned. But might be a feature request to enhance this feature.
@Peter and @Henri
I'm trying to replicate this issues now. Update here and in the tracker when I have something...
Thanks
Well I'm out of time now, replicating in my env is easy. But in a small zul is quite hard. I'll try again tomorrow.
Now, the Issue 1. was solved by changing width and height attribute to v and h flex.
Is there any recommendation to stick with one on this? Or mixing them should not create any problem?
Regards,
Madruga
@Madruga,
If you can provide us a link to test on. It is also OK. You can post here or mail the link and the steps to replicate the issue to henrichen AT zkoss DOT org.
Hi Henri,
Thank you for the attention.
I'm sorry for not digging on this back when I reported, I was really busy.
Now I have some spare time, I'll test this issues with Z 5.0.3 FL
Autopaging is still a bit crazy for me, issue 1 was solved by h and vflex set up. But I can see issues 2 and 3 in my complex app.
I believe that the problem on autopaging is that I use with databind, and relies on obj.toString(), sometimes the String is just one line, sometimes 2 or more lines, than autopaging goes haywire.
I'll see what I can do (will try to replicate with a simple zul, or set up a live app for you guys to look at the issue)
About the renderdefer, I think that the issue is miss sync with renderdefer and server push. Probably not a issue right? Just a miss use case. Not involving the component that is updated by the server push in the renderdefer everything work as expected.
I removed the listcell which relies on toString() and let only the cells were the content has almost the same size.
The result was only one line on all generated listitems, and autopaging works flawlessly.
Got it a simple zul which replicates this.
Reporting to the tracker now.
Madruga,
Thanks for the sample code. Now I can replicate the issue.
Looks the text wrapping(which will change the row height) and vertical
scrollbar that cause the text wrapping confuse the page size calculation.
In the mean time, you can work around this by set text to be no wrap in the cell.
... <listcell style="white-space:nowrap" .../> <listcell style="white-space:nowrap" .../> <listcell style="white-space:nowrap" .../> ...
Asked: 2010-05-14 15:03:23 +0800
Seen: 1,054 times
Last updated: Jun 29 '10