Skip to content

Frame, View Frame and Data Frame sizes #46

@dkrasner

Description

@dkrasner

Main Issue

There are a number of issues dealing with views and sheets and the underlying data store. Some have been noted: issue #45 #29 #40 and #21 are examples.

The main crux is the following (I believe):

There is no guarantee that the DF is big enough. For example, I could start with a small sheet, example 5x5 (dataFram.size = Point([5,5])) and then increase the number of rows or columns in GridSheet (through resizing for example). This will cause all sorts of dataFrame.getAt errors for points which it does not contain.

You can try to fix this with something like this but other issues will still creep up.

For example, if you are at the bottom of a sheet (you scroll all the way to bottom) and then you enlarge resize you end up re-rendering (GridSheet.render()) to the top of the sheet and no columns or rows are added. Here you would expect that you either simply cannot resize bigger, or you end up with more rows/columns. But regardless you should not loose your view of the data, going back to [0, 0].

We can do the infinite grow options, or the google sheets "add rows/columns" context menu say.

In the end you should never get into a state where copy/paste, etc, fail b/c of "point not in frame" errors or "can't deal with undefined"

This might also be tied to the refactoring of dataFrame.store to be an async retrieval.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions