Tables + displayCollection

[ConvertFromOldNGs]

by CassMan >> Wed, 21 Nov 2007 10:04:02 GMT

Hi Guys,

I just thought i would update you on this odd problem. Basically, i was informed that it was because i was running it as a web application, apparantly that reacts very differently to the way you display collections in a list. Sorry i didn't mention the fact that it was web-related at the start - i wasn't expecting that to make a big difference.....

Thanks for all your help!

Cass

[ConvertFromOldNGs]

by BeeJay >> Thu, 22 Nov 2007 3:33:15 GMT

That does help to explain why you were apparently encountering a problem with what is a relatively simple to implement Jade feature.

.... tucks away a mental reminder to remember to ask what the presentation mechanism is in future for any similar queries...

Cheers,
BeeJay.

[ConvertFromOldNGs]

by Torrie Moore >> Thu, 20 Sep 2007 0:59:40 GMT

--- Snip ---

On a completely separate note, if you have the update parameter of displayCollection set to false and the objects in the collection are updated by another user, your table won't update automatically.

--- Snip ---


As I understand it, the update property only will update the table if the collection itself is updated. This occurs when an object is added or removed or when a member's key property is changed causing the collection to be reordered. Updates made to the objects in the collection do not cause the table to be refreshed.

Torrie

[ConvertFromOldNGs]

by John Munro >> Thu, 20 Sep 2007 20:40:39 GMT

Very true, I meant when the collection was updated - had a phrasing malfunction

John

[ConvertFromOldNGs]

by CassMan >> Thu, 20 Sep 2007 8:31:44 GMT

Initially, i set the scrollBars property to both. But like most things, i also tried setting it to just Vertical. But that didn't change anything either.

Regarding bcontinue i didn't set this at all - i believe it is defaultly set to 'true' though. I didn't actually try forcing this to a value at any stage either to be honest.

As is being discussed in this thread now; the table wasn't needing to be updated dynamically. It is used purely for reference and doesn't even need the ability to allow user updates; apart from an "Ok" button, it was the only thing on a separate form.

Thanks for all your help.

[ConvertFromOldNGs]

by John Munro >> Thu, 20 Sep 2007 20:44:44 GMT

So it fills the table with as many rows as are visible and gives you a scrollbar, but when you drag the scrollbar nothing happens?

John

[ConvertFromOldNGs]

by CassMan >> Wed, 3 Oct 2007 14:40:37 GMT

Hi John,

Sorry for the late reply.

Sort of. It populated the table up to the number of visible rows and then displayed a 'full' scrollbar. 'Full' meaning that it couldn't be moved - it was just there!

I managed to fix this problem in the end by the way, i simply did it manually by calling the displayRow method for all instances. In essence making my own displayCollection method. And that worked fine.

Rich

[ConvertFromOldNGs]

by BeeJay >> Thu, 4 Oct 2007 4:28:56 GMT

It's probably still worth perservering with working out why it's not working as expected for you as your current fix won't work efficiently with a much larger collection being displayed. It definitely works as expected with the ability to scroll every time I have used displayCollection to populate a table, so it would be interesting to see why you are having this unusual behaviour.

Are you able to reproduce this in a sample schema directly off RootSchema? If so, perhaps attach an extract of the sample schema so we can take at your sample code?