Hi Formspider Team,

We are changing our application to make use of the infinite scroll feature. We encounter the following issue:

  • We have a panel with a grid. Datasource is on infinite scroll / Query as needed / initial fetch size 20.
  • In our menubar there is a next_record button (calls api_datasource.next_record). When we do next_record on the last record that is initially shown on screen (in this case record nr 20), then the next record in the datasource is fetched (we can see that the detail datasource change accordingly), but the next set of 20 records are not fetched to the grid.

So we can continue to the next record, so i guess in the datasource table the next set of records are fetched, but the next set (and thus the current record) is not show in the grid.

On another screen where we show only 1 record at a time, we cannot navigate to the next record now. In 1.5 we used a bit of a hack to make single record navigation possible. We set datasource to paging and fetch 1 record on a page, and then do next_page, but that is a bit of a hack. Using infinite scrool with a fetch size of 1 seems more appropiate.

Is there a workaround, am i missing something or is this a bug?

Bitt offtopic, but i noticed another thing with infinite scroll: there is always a scrollbar on the right side of the grid, even is the number of records fetched fit in the visible grid size. Is this by design, or can it be fixed?

Thanks,
Michiel

asked 27 Nov '13, 05:05

Michiel%20A's gravatar image

Michiel A
5161749
accept rate: 13%


Hi Michiel,

The Datasource Row Navigation API's are not supported for Infinite Scroll at this time. Thank you for bringing this to our attention. We were supposed to mention this limitation in the tutorial but forgot to do so. I'll update the tutorial.

Kind Regards,
Yalim

link

answered 27 Nov '13, 05:18

Yalim%20Gerger's gravatar image

Yalim Gerger ♦♦
1.8k5
accept rate: 15%

Hi Yalim,

Can i call the procedure the key-down on a grid calls? The key-down works fine.

Thanks,
Michiel

(27 Nov '13, 05:34) Michiel A

Sorry I did not understand the question.

(27 Nov '13, 05:36) Yalim Gerger ♦♦

I mean, the arrow keys (up / down) on a grid work fine. Is it possible to simulate this event somehow, so we can do that instead of api_datasource.nextrecord? (api_event maybe?) Or you plan to make the datasource row navigation work with infinite scroll on the next release?

(27 Nov '13, 07:10) Michiel A

There isn't a way to do this with an API but there might be a hack. I'll get back to you on that.

(27 Nov '13, 07:17) Yalim Gerger ♦♦

Thanks, i would appreciate that.

(27 Nov '13, 07:28) Michiel A

Hi Yalim, one additional comment on the navigation API's : api_datasource.lastRow is something to think about also. (aside of the fact if you would want to do it on an infinite scroll grid, but it should work i think..)

(27 Nov '13, 08:01) Michiel A
showing 5 of 6 show 1 more comments

Regarding the 2nd question. The Grid doesn't always show a scroll bar. Since it works in infinite scroll mode, it tries to give the user the ability to retrieve more rows, if there might be any. Could you please answer these questions:

how many rows does your query return in total? what is your first fetch size in the datasource? how many rows does your grid fit without a scroll bar?

Kind Regards, Yalim

link

answered 27 Nov '13, 05:26

Yalim%20Gerger's gravatar image

Yalim Gerger ♦♦
1.8k5
accept rate: 15%

Hi Yalim,

Query return 3 rows
Set first fetch size is 10
Grid shows 20 records easily, so no need for scrollbar

(27 Nov '13, 05:33) Michiel A

OK. I tried it. Do you mean to say that you see an inactive scroll bar? In that case, yes, there is an inactive scroll bar. we could hide it I guess. I'll ask the team if there is a specific reason we've done this.

(27 Nov '13, 05:38) Yalim Gerger ♦♦

Correct, there is an inactive scrollbar. That is what i meant. Not a very big deal, but i would be nice if the scrollbar could be hidden when it is not needed, like in the other options.

(27 Nov '13, 07:07) Michiel A
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×5
×4
×1

Asked: 27 Nov '13, 05:05

Seen: 1,160 times

Last updated: 27 Nov '13, 08:01


© Copyright Gerger 2017