ESOUI

ESOUI (https://www.esoui.com/forums/index.php)
-   General Authoring Discussion (https://www.esoui.com/forums/forumdisplay.php?f=174)
-   -   PTS 1.5.1 API changes (100009 to 100010 diff) (https://www.esoui.com/forums/showthread.php?t=2370)

Garkin 11/01/14 11:29 AM

PTS 1.5.1 API changes (100009 to 100010 diff)
 
  • New Functions:
    Warning: Spoiler

  • Removed Functions:
    Warning: Spoiler

  • New Events:
    Warning: Spoiler

  • Removed Events:
    Warning: Spoiler

  • New Constants:
    Warning: Spoiler

  • Removed Constants:
    Warning: Spoiler

  • Added EsoStrings:
    Warning: Spoiler

  • Removed EsoStrings:
    Warning: Spoiler

  • New Tables:
    Warning: Spoiler

  • Removed Tables:
    Warning: Spoiler

  • New Userdata:
    Warning: Spoiler

  • Removed Userdata:
    Warning: Spoiler


Garkin 11/04/14 10:05 AM

Documentation does not contain information that two functions got a new return value:
  • GetPOIMapInfo(luaindex zoneIndex, luaindex poiIndex)
    Returns: number normalizedX, number normalizedZ, MapDisplayPinType poiType, textureName icon, bool isShownInCurrentMap

  • GetFastTravelNodeInfo(luaindex nodeIndex)
    Returns: bool known, string name, number normalizedX, number normalizedY, textureName icon, textureName:nilable glowIcon, PointOfInterestType poiType, bool isLocatedInCurrentMap

DuchessOfKvetch 11/04/14 10:49 AM

I think ZO_OptionsWindow.controlTable also went bye-bye, seeing as how this is the line breaking in Borrower and Lender, even after updating to use the backward-compatible LibAddonMenu.

Also, can someone sticky these PTS change threads? The last one pinned is from 1.23.

Garkin 11/04/14 11:23 AM

Quote:

Originally Posted by DuchessOfKvetch (Post 12955)
I think ZO_OptionsWindow.controlTable also went bye-bye, seeing as how this is the line breaking in Borrower and Lender, even after updating to use the backward-compatible LibAddonMenu.

Also, can someone sticky these PTS change threads? The last one pinned is from 1.23.

ZO_OptionsWindow.controlTable is now KEYBOARD_OPTIONS.controlTable

Ayantir 11/07/14 01:18 PM

I really think we need to put in the same topic for each update

Patch note (for Users)
API changes (for devs by ZOS)
API changes (for devs with diff made by community)

And a sticky in some post with links with each topic (release, u1/2/3/4/5/6..etc)

It's actually hard to find doc about X or Y function..

mctaylor 11/08/14 06:04 PM

Quote:

Originally Posted by Ayantir (Post 13064)
I really think we need to put in the same topic for each update
[...]
It's actually hard to find doc about X or Y function..

You mean like this: APIVersion (from the Wiki, feel free to fill in missing information)?

The Wiki works best if people (i.e. everyone and anyone) update it as they discover something missing.

=====

I believe like BankerShutup and Borrower and Lender are affected by some additional changes to the Audio Settings.

In particular, I haven't figure out if:

Lua Code:
  1. OPTIONS_PANEL_AUDIO = 2
replaced(?) with
Lua Code:
  1. SETTING_PANEL_AUDIO = 0

is relevant.

But I suspect that the audio settings might be better controlled by
Lua Code:
  1. Options_Audio_???.data.value;
(e.g.
Lua Code:
  1. Options_Audio_MasterVolume.data.value;
) from the userdata rather than the
Lua Code:
  1. KEYBOARD_OPTIONS.controlTable[SETTING_PANEL_AUDIO][AUDIO_SETTING_AUDIO_VOLUME]
.

Garkin 11/08/14 08:52 PM

Quote:

Originally Posted by mctaylor (Post 13103)
You mean like this: APIVersion (from the Wiki, feel free to fill in missing information)?

The Wiki works best if people (i.e. everyone and anyone) update it as they discover something missing.

=====

I believe like BankerShutup and Borrower and Lender are affected by some additional changes to the Audio Settings.

In particular, I haven't figure out if:

Lua Code:
  1. OPTIONS_PANEL_AUDIO = 2
replaced(?) with
Lua Code:
  1. SETTING_PANEL_AUDIO = 0

is relevant.

But I suspect that the audio settings might be better controlled by
Lua Code:
  1. Options_Audio_???.data.value;
(e.g.
Lua Code:
  1. Options_Audio_MasterVolume.data.value;
) from the userdata rather than the
Lua Code:
  1. KEYBOARD_OPTIONS.controlTable[SETTING_PANEL_AUDIO][AUDIO_SETTING_AUDIO_VOLUME]
.

Options were completely reworked, so if you have used any non-standard method of getting settings it probably wont work anymore.

Standard way is using functions GetSetting and SetSetting.

* GetSetting(*integer* _system_, *integer* _settingId_)
** _Returns:_ *string* _value_

* SetSetting(*integer* _system_, *integer* _settingId_, *string* _value_, *integer* _setOptions_)

In your case it would be:
Lua Code:
  1. --to get a value:
  2. local volume = tonumber(GetSetting(SETTING_TYPE_AUDIO, AUDIO_SETTING_AUDIO_VOLUME))
  3. --to set a value:
  4. SetSetting(SETTING_TYPE_AUDIO, AUDIO_SETTING_AUDIO_VOLUME, volume)
volume is a number between 0 and 100.


All times are GMT -6. The time now is 09:00 PM.

vBulletin © 2020, Jelsoft Enterprises Ltd
© 2014 - 2019 MMOUI