macros:function:handles.playbacks.nextpage
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| macros:function:handles.playbacks.nextpage [2018/08/24 10:16] – created icke_siegen | macros:function:handles.playbacks.nextpage [2018/09/10 12:47] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 17: | Line 17: | ||
| **This function does not fully work as Avolites never intended these buttons to be paged.\\ | **This function does not fully work as Avolites never intended these buttons to be paged.\\ | ||
| Handles.Playbacks.NextPage() ) doesn’t increment, but always goes to page 1..** | Handles.Playbacks.NextPage() ) doesn’t increment, but always goes to page 1..** | ||
| + | |||
| + | See also http:// | ||
| + | |||
| + | >The next and previous page functions unfortunately do not work properly for workspace windows as they attempt to loop around the maximum number of pages. For the playback faders this is 60, so when you are on that page pressing next page will take you to page 1 and the opposite is true with previous page. However workspace windows do not have a predefined maximum page number so this is set to zero which means that next page always loops around to page 1 and when on page 1 previous page will take you to the maximum page which is zero. One work around is to set the page directly e.g.: | ||
| + | > | ||
| + | >< | ||
| + | >Note however that this doesn' | ||
| == Example in == | == Example in == | ||
macros/function/handles.playbacks.nextpage.1535105781.txt.gz · Last modified: 2018/08/24 10:16 (external edit)