Posters in general do not pose an issue, but there are two aspects of use of which to be aware
- some visualisations may either/both use a lot of computational effort or call on very large datasets. Tinderbox can use lots of processing power; a more likely limit may occur in terms of the overall CPU power/RAM of the host Mac and the demands of other currently running programs.
- posters can make significant demands inside the map view, which is already quite demanding. Some performance optimisations are already in place, but it may be good to understand them. If a note is well off-screen, i.e. outside the currently visible area of the map, it loses its poster (i.e. the poster is not calculated/drawn) and regains the poster only as the note approaches the viewport (i.e. so it is drawn ready when the poster note is scrolled into view).
- any visible poster is refreshed when the map is laid out or refreshed.
- to reload a poster, click the tab label area of the current tab, which asks Tinderbox to re-draw the current map. Additionally, if a poster is asked to reload its data, it will wait a minimum of five seconds from the most recent reload—this avoids unnecessary re-calculation due to rapid multiple clicks, e.g. double-clicking the tab rather than single-clicking it.
In summary, when planning poster use consider both the effect of each individual poster and the number of posters in use within a map—or at least the number visible on screen at the same time.