WoW:API ItemTextNextPage: Difference between revisions

From AddOn Studio
Jump to navigation Jump to search
mNo edit summary
m (Move page script moved page API ItemTextNextPage to API ItemTextNextPage without leaving a redirect)
 
(5 intermediate revisions by 5 users not shown)
Line 1: Line 1:
<center>'''ItemTextNextPage''' - ''Documentation by [[User:Flickering|Flickering]]''</center>
{{wowapi}}


Request the next page of an Item Text
Request the next page of an Item Text
Line 9: Line 9:


=== Returns ===
=== Returns ===
:<i>nil</i>
:''nil''




Line 15: Line 15:
: This simply requests the next page, you will receive an ITEM_TEXT_READY event when the new page is ready.
: This simply requests the next page, you will receive an ITEM_TEXT_READY event when the new page is ready.


: Try only to call this after receiving an ITEM_TEXT_READY event for the current page, and dont call it IN the event handler for that event, things get a little odd (Looks like a synchronization issue in the client) and your page cache might get corrupted.
: Try only to call this after receiving an ITEM_TEXT_READY event for the current page, and don't call it IN the event handler for that event, things get a little odd (Looks like a synchronization issue in the client) and your page cache might get corrupted.


: Does nothing if called while viewing the last page.
: Does nothing if called while viewing the last page.
Line 21: Line 21:
----
----
__NOTOC__
__NOTOC__
{{Template:WoW API}}
[[Category:API Functions|ItemTextNextPage]]
[[Category:API Item Text Functions|ItemTextNextPage]]

Latest revision as of 04:46, 15 August 2023

WoW API < ItemTextNextPage

Request the next page of an Item Text

ItemTextNextPage()

Parameters[edit]

Arguments[edit]

()

Returns[edit]

nil


Details[edit]

This simply requests the next page, you will receive an ITEM_TEXT_READY event when the new page is ready.
Try only to call this after receiving an ITEM_TEXT_READY event for the current page, and don't call it IN the event handler for that event, things get a little odd (Looks like a synchronization issue in the client) and your page cache might get corrupted.
Does nothing if called while viewing the last page.