ToggleGroupFrame (and Companion Unit Frame) : Unit Mods : Elder Scrolls Online AddOns

(3 Kb)

Download

Updated: 09/18/24 06:58 AM

Add Favorite

Install Help

Pictures

File Info

Compatibility:	Update 43 (10.1.0) Gold Road (10.0.0) Scions of Ithelia (9.3.0) Endless Archive (9.2.5) base-game patch (9.1.5) Necrom (9.0.0) Scribes of Fate (8.3.5)
Updated:	09/18/24 06:58 AM
Created:	08/05/23 01:25 PM
Monthly downloads:	190
Total downloads:	1,422
Favorites:	1
MD5:

10.1.0

ToggleGroupFrame (and Companion Unit Frame)

Version: 1.4.0

by: Saint-Ange [More]

Cycle through 4 different group frame visibility states with one keybind or slash command /tgf

Always Show
Always Hide
Show but Hide in Combat
Hide but Show in Combat

Options menu:

Display switch notification in chat system
Display switch notification on screen
Do not display any switch notification

The group frame visibility state is now saved per character and per server

WARNING! To migrate from v1.3.2 (or lower) to 1.4.0:
WHILE THE GAME IS COMPLETELY CLOSED delete ToggleGroupFrame's file in

Documents\Elder Scrolls Online\live\SavedVariables

Library required: LibAddonMenu-2.0

1.4.0 API Update 43
Recoded from scratch
One keybind to cycle through visibility states
Options menu
Save per character and per server
Library required LibAddonMenu-2.0
1.3.2 API Update 42
1.3.1 Terrible mistakes were made. Saved variables not yet working as intended.
1.3.0 API Update 41. Added a second toggle to show/hide in combat while initialy hidden.
1.2.1 Should follow a propper and more structured approach to load this addon's code, thanks to Baertram.
1.2.0 Hide the Group Frame by default at the start of the game or after a reloadui. Shortened the slash command.
1.1.0 API Update 40 - Secret of the Telvanni.
1.0.0 Release.

Optional Files (0)

Archived Files (5)

File Name	Version	Size	Uploader	Date
ToggleGroupFrame (and Companion Unit Frame)	1.3.2	2kB	Saint-Ange	06/13/24 04:45 AM
ToggleGroupFrame (and Companion Unit Frame)	1.3.1	2kB	Saint-Ange	03/14/24 03:04 PM
ToggleGroupFrame (and Companion Unit Frame)	1.2.1	2kB	Saint-Ange	02/14/24 02:05 AM
ToggleGroupFrame (and Companion Unit Frame)	1.1.0	1kB	Saint-Ange	11/01/23 01:17 AM
ToggleGroupFrame (and Companion Unit Frame)	1.0.0	1kB	Saint-Ange	08/05/23 01:25 PM

Comment Options

02/14/24, 02:15 AM

Saint-Ange

Forum posts: 22

File comments: 27

Uploads: 4

Hi Baertram,

Thank you very much for your help!

Lua code is typically executed in a sequential manner, starting from the top of the script and moving down line by line. However, there are nuances to this process:

1. **Sequential Execution**: Lua executes code sequentially by default, meaning it starts at the top of the script and moves down, line by line, executing each statement or block of code as it encounters them.

2. **Control Structures**: Lua supports control structures like loops (for, while) and conditionals (if-else), which can alter the flow of execution. When Lua encounters these structures, it may jump to different parts of the script based on certain conditions or iterate over sections of code multiple times.

3. **Function Calls**: Lua allows defining and calling functions. When a function is called, Lua temporarily suspends execution of the current code block, executes the function's body, and then returns to where it left off in the original code.

4. **Callbacks and Event Handling**: In Lua environments like game development or GUI programming, code may not follow a strictly sequential execution model. Instead, certain parts of the code may be executed in response to events triggered by user input, system events, or other asynchronous processes.

5. **Coroutines**: Lua also supports coroutines, which are a way to achieve cooperative multitasking. Coroutines allow suspending and resuming execution at certain points, enabling more complex control flows and concurrency patterns.

So, while Lua typically executes code from top to bottom, the presence of control structures, function calls, event handling mechanisms, and coroutines can introduce non-linear execution paths.

02/13/24, 03:44 PM
Baertram Super Moderator Forum posts: 5190 File comments: 6261 Uploads: 78	Hi Saint-Ange, your addon should not put the code directly into the lua file but you must use the EVENT_ADD_ON_LOADED properly for YOUR addon to load, and in there do your addon stuff then. Else it could be that code your addon needs was not finished yet and it fails to work properly, and or libraries you might add won't work. Described here for example: https://wiki.esoui.com/SimpleNotebookTutorial/part3 Remember to unregister your EVENT_ADD_ON_LOADED again after your addon was loaded, else it fires again and again for each other addon. Please change that code lines accordingly, thanks.

Report this File