Could the InfiniteScrolledMap callback allow custom data?

[jembishop]

Hey there!

An issue I am facing with InfiniteScrolledMap is that I want the lookup of the tile to depend on the current level. In order to do this I can either:

• Recreate the InfiniteScrolledMap on every level change.
• Pass a mutable reference into the closure for the current level struct.
• Use a RefCell to wrap the level struct and pass an immutable reference to the closure.

The problems are respectively:

• This seems a bit clunky and perhaps inefficient? It is the method use on The Hat Chooses the Wizard though.
• This is a no go as I cannot create 2 mutable references.
• This is my current solution. It's a bit annoying, and also inefficient.

Maybe an alternative would be to have the closure in InfiniteScrolledMap accept another argument which is custom data. On the set_pos and init calls, this data would then be fed to the closure to do the tile updating.

What do guys you think?

[paulrouget]

This seems a bit clunky and perhaps inefficient? It is the method use on The Hat Chooses the Wizard though.

I think recreating to InfiniteScrolledMap is the "right way". Looking at the code, it doesn't seem inefficient, and if it is, a function to swap the closure would do (as it would allow you to recapture the new level).

[corwinkuiper]

If you have a slice of levels, then the index of the currently loaded level index can go in a Cell, which should be pretty cheap.