So, if you ever tried to implement some kind of page browsing functionality in a dashboard to provide large datasets for
spreadsheet-components, that have no native scrollbar, you might have noticed some strange behaviour with the toggle-button component in Xcelsius 2008.
I observed two effects, that nearly drived me 
The first effect i have noticed, is that if you are using a toggle button to implement page-scroll functionality, which drives an offset, it ends up in some kind of infinite loop. This is cause by the fact, that a toggle-button natively has two-source cells and two events. If you override the fact of two source-cells with the use of the same values for both cells, you might get in trouble.
Check out the following example and see what happened: (hit the link below and use the forward button)
A Workaround until Xcelsius 2008 SP3 was to limit the number of pages to a fixed value and add two scroll-toggle-button for every page (back and forward), which were controlled by dynamic visibility.
But here we encouter the second issue:
By initializing the components Xcelsius seem to execute the toggle-button once and set the references. The effect on the page browse functionality is, that on first run the dashboard runs through all pages and initially presents the end-user the last page. So, let me tell you, that there is also a workaround for the workaround, which could call "stop or block component", but let's face the future and the new features of Xcelsius 2008 SP3.
In Xcelsius 2008 SP3, there is a new component called "Push Button". (Proven below 
)
The difference between the toggle and the push button, is that the push button only has one event and so the problems above won't occur.
Check out the second showcase with the push-button below, and be impressed by a working page browse functionality. It's Magic 
RSS Feeds
