Quote:
Originally Posted by crutledge
I did somethng very similar for a gov't contract many years ago. On load, each entity is given sequential number. When the user scrolled data was sent from one display to the other and caused an update. This occured On Click and on Scroll. I don't remember the details and I do remember using some special tools, but maybe the idea is applicable here. BTW, the OS wasn't Windows.
|
Oh I have no problems sending data from one View to the other: Qt's Signals&Slots mechanism works great here. It's just that even though both Views use the same code, CV shows it directly, while BV renders it out. The vertical size of the content is completely different. And it's not proprotional, so I can't just say "Ok, if BV is 2/3 down the page, CV needs to be 2/3 down the page too". An image takes up a lot of space in BV but only a line of code in CV.
The last thing idea I came up with was to track what element was in the center of the any view and try to make the other view match that. But this would be rather computationally expensive. That, and I don't have clue how I would implement it.
Adobe Dreamweaver seems to take the caret position approach I talked about. This is probably the route I'm going to take.