Sliding Interface MKIII (CMS) - Revision history

AFRLme at 11:35, 15 September 2022

2022-09-15T11:35:38Z

AFRLme at 12:07, 29 August 2022

2022-08-29T12:07:40Z

AFRLme at 12:06, 29 August 2022

2022-08-29T12:06:57Z

AFRLme at 02:34, 15 August 2022

2022-08-15T02:34:58Z

AFRLme at 02:32, 15 August 2022

2022-08-15T02:32:46Z

AFRLme at 02:32, 15 August 2022

2022-08-15T02:32:17Z

AFRLme at 02:23, 15 August 2022

2022-08-15T02:23:28Z

AFRLme at 02:14, 15 August 2022

2022-08-15T02:14:34Z

AFRLme at 02:13, 15 August 2022

2022-08-15T02:13:18Z

AFRLme at 02:09, 15 August 2022

2022-08-15T02:09:58Z

@@ Line 3: / Line 3: @@
 ! style="text-align:left" | Name !! style="text-align:left" | Type !! style="text-align:left" | By
 |-
-| Sliding Interface MKIII || Definition || AFRLme
+| Sliding Interface MKIII || Definition || [https://www.patreon.com/AFRLme AFRLme]
 |}
@@ Line 29: / Line 29: @@
 Written by AFRLme [Lee Clarke]
 -- + --
-afrlme@outlook.com | https://afrl.me
+email: afrlme@outlook.com
 -- + --
 This script is donation optional. In game credit is non-negotiable.
@@ Line 79: / Line 82: @@
 Written by AFRLme [Lee Clarke]
 -- + --
-afrlme@outlook.com | https://afrl.me
+email: afrlme@outlook.com
 -- + --
 This script is donation optional. In game credit is non-negotiable.

@@ Line 12: / Line 12: @@
 | ''Quick note #1: The interface will only slide in or out if the interface is fully in or out. You can't interrupt it once you start it sliding. The only way to interrupt it & maintain the correct speed would require math calculations to get the current percentage between the start position & target position, which in this case is more hassle than it's worth.''
 |-
-| ''Quick note #2: Visionaire Studio supports most of the easing options listed on this [https://www.visionaire-studio.com/luadocs/lua.html#easing page]''.
+| ''Quick note #2: Visionaire Studio supports all of the easing options listed on this [https://www.visionaire-studio.com/luadocs/lua.html#easing page]''.
 |}

@@ Line 12: / Line 12: @@
 | ''Quick note #1: The interface will only slide in or out if the interface is fully in or out. You can't interrupt it once you start it sliding. The only way to interrupt it & maintain the correct speed would require math calculations to get the current percentage between the start position & target position, which in this case is more hassle than it's worth.''
 |-
-| ''Quick note #2: Visionaire Studio supports most of the easing options listed on this [https://easings.net page], however in Visionaire Studio easings are written like this: <span class="green">easeQuintInOut</span>, instead of this: <span class="green">easeInOutQuint</span>''.
+| ''Quick note #2: Visionaire Studio supports most of the easing options listed on this [https://www.visionaire-studio.com/luadocs/lua.html#easing page]''.
 |}

@@ Line 22: / Line 22: @@
 === Instructions ===
-a. Add this script into the script section of the Visionaire Studio editor & set as a defintion type script...
+. Add this script into the script section of the Visionaire Studio editor & set as a defintion type script...
 <hr>
 <syntaxhighlight lang="lua">
@@ Line 54: / Line 54: @@
 </syntaxhighlight>
 <hr>
-b. You need to edit the script above & insert the names of any interfaces you want to be able to slide in & out. You will also need to define the default position of the interfaces [In] & the target position of the interfaces [Out]. Don't forget to include the duration it should take the interface to slide in or out, or the easing you want to use.
+{| class="ts"
+|-
 . To use this script you need to create an execute a script action part inside of the key actions, mouse enters/leave actions, command actions, etc. that you want to use to slide an interface out with & then you would insert a line of code that looks like something along the lines of this...
 <hr>

@@ Line 12: / Line 12: @@
 | ''Quick note #1: The interface will only slide in or out if the interface is fully in or out. You can't interrupt it once you start it sliding. The only way to interrupt it & maintain the correct speed would require math calculations to get the current percentage between the start position & target position, which in this case is more hassle than it's worth.''
 |-
-| ''Quick note #2: It's technically possible to slide an interface in or out with a single line of code, using the to() tweening function that I am using in the function examples below. However, we are using the functions so that we have less to type overall & the function can be used for multiple interfaces instead of having to write new code blocks for additional functions - just think of it as a workflow function used to save a bit of time in the long run.
+| ''Quick note #2: Visionaire Studio supports most of the easing options listed on this [https://easings.net page], however in Visionaire Studio easings are written like this: <span class="green">easeQuintInOut</span>, instead of this: <span class="green">easeInOutQuint</span>''.
 |}

@@ Line 159: / Line 159: @@
 ! style="text-align:left" | Name !! style="text-align:left" | Description
 |-
-| [[media:sliding_interface_vs4.zip|to add]] || A working example of the script in action. ''Visionaire Studio 5.1.9.2+'' required to run the included .ved file(s).
+| [[media:sliding_interface_mk3.zip|sliding_interface_mk3.zip]] || A working example of the script in action. ''Visionaire Studio 5.1.9.2+'' required to run the included .ved file(s).
 |}{{toc}}

@@ Line 99: / Line 99: @@
 </syntaxhighlight>
 <hr>
-a. To use this script you need to create an execute a script action part inside of the key actions, mouse enters/leave actions, command actions, etc. that you want to use to slide an interface in or out with & then you would insert a line of code that looks like something along the lines of this...
+. To use this script you need to create an execute a script action part inside of the key actions, mouse enters/leave actions, command actions, etc. that you want to use to slide an interface in or out with & then you would insert a line of code that looks like something along the lines of this...
 <hr>
 <syntaxhighlight lang="lua">

@@ Line 88: / Line 88: @@
 --]]
-function slideInt(int, dir, spos, tpos, duration, easing)
+function slideInt(int, spos, tpos, duration, eIn, eOut)
-   if dir and (Interfaces[int].Offset.x == spos.x and Interfaces[int].Offset.y == spos.y) then -- slide out
+   if Interfaces[int].Offset.x == spos.x and Interfaces[int].Offset.y == spos.y then -- slide out
-     Interfaces[int]:to(duration, { Offset = {x = tpos.x, y = tpos.y} }, easing)
+     Interfaces[int]:to(duration, { Offset = {x = tpos.x, y = tpos.y} }, eOut)
-   elseif not dir and (Interfaces[int].Offset.x == tpos.x and Interfaces[int].Offset.y == tpos.y) then -- slide in
+   elseif Interfaces[int].Offset.x == tpos.x and Interfaces[int].Offset.y == tpos.y then -- slide in
-     Interfaces[int]:to(duration, { Offset = {x = spos.x, y = spos.y} }, easing)
+     Interfaces[int]:to(duration, { Offset = {x = spos.x, y = spos.y} }, eIn)
    end
@@ Line 99: / Line 99: @@
 </syntaxhighlight>
 <hr>
-a. To use this script you need to create an execute a script action part inside of the key actions, mouse enters/leave actions, command actions, etc. that you want to use to slide an interface out with & then you would insert a line of code that looks like something along the lines of this...
+a. To use this script you need to create an execute a script action part inside of the key actions, mouse enters/leave actions, command actions, etc. that you want to use to slide an interface in or out with & then you would insert a line of code that looks like something along the lines of this...
 <hr>
 <syntaxhighlight lang="lua">
-slideInt("int_example", true, {x = 390, y = 710}, {x = 390, y = 530}, 1000, easeBounceOut)
+slideInt("int_example", {x = 390, y = 710}, {x = 390, y = 530}, 1000, easeQuintIn, easeBounceOut)
 </syntaxhighlight>
 <hr>

@@ Line 64: / Line 64: @@
 <hr>
 <syntaxhighlight lang="lua">
-slideInt("int_example_1", true)
+slideInt("int_example_1")
 </syntaxhighlight>