| Summary: | Missing notifications with sychronized scrolling of 2 grids (one without scrollbar) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | David Császár <csaszar> | ||||||
| Component: | Nebula | Assignee: | Chris Gross <cgross> | ||||||
| Status: | RESOLVED DUPLICATE | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | tom.schindl | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
David Császár
Hi David, Can you attach a snippet of what you're trying to do. The scrollbar proxies weren't meant for this use case but may work. The lack of a horz proxy may account for 3. -Chris Created attachment 76507 [details]
snippet demonstrating the bug
my current workaround is included, just uncomment and re-run
Created attachment 76544 [details]
new example
David - here is a different technique to accomplish the synchronized scrolling. The scrollbar proxies shouldn't really be used for this kind of thing. Let me know if this example works for you.
it doesn't work for me. in my case the left grid doesn't have scrollbars at all (SWT.NONE). so i'm not able to attach scroll event handlers to this grid. Then you can just remove the scrollbar listener for that grid. The remaining code should work. it doesn't. obviously the line grid1.setTopIndex(grid2.getTopIndex()); has no effect if grid1 has no scrollbar. grid1 (without bar) also doesn't scroll when the grid cursor reaches the bottom. Oh.. right. I didn't think about that. Then the code you have seems fine. The scrollbar proxies aren't intended for things like this but it seems to work ok. I would change your workaround to use selection listeners rather than traverse listeners but otherwise it seems ok. Are there more issues or were you just asking for an easier way to support this? an easy (standard, recommended) way would be nice. in fact my 1st (naive, derived from some other snippet) try looked a lot like the one you suggested. so maybe this is the root cause for this bug, and comment 0 just a symptom. apart from this the workaround is completely achieving what i want. Ok. I'll leave this item open until there is an easier way to achieve this but for now your workaround is the only solution. Is the real feature you need the one in no #166089? I'll close this if you don't agree please reopen. *** This bug has been marked as a duplicate of bug 166089 *** |