Plugins - Revision history

EK at 22:47, 19 February 2025

2025-02-19T22:47:24Z

EK at 11:33, 27 November 2023

2023-11-27T11:33:34Z

EK at 23:09, 18 August 2023

2023-08-18T23:09:20Z

EK at 10:13, 17 April 2023

2023-04-17T10:13:24Z

EK at 13:03, 13 April 2023

2023-04-13T13:03:22Z

EK at 09:24, 13 April 2023

2023-04-13T09:24:46Z

Show changes

EK at 10:15, 24 February 2023

2023-02-24T10:15:59Z

EK: Created page with "link= Visionaire Studio features a plugin system which lets you develop your own action parts. Plugins get installed per project, so when sta..."

2023-01-16T14:05:18Z

Created page with "right|25px|link= Visionaire Studio features a plugin system which lets you develop your own action parts. Plugins get installed per project, so when sta..."

New page

[[File:plugin25n.png|right|25px|link=]]
Visionaire Studio features a plugin system which lets you develop your own action parts. Plugins get installed per project, so when starting a new project you have to install plugins you wish to use (again), even if you used them before in another project. Open the plugin section through the jigsaw icon in the toolbar to see all plugins currently installed or ready to get installed. You can uninstall them here, too, of course.

Once you have installed a plugin you are ready to use the newly added action part(s). Note that you will not find these custom action parts in the action part selection dialog. They will only be added to the bottom of the action part list which is available ''after'' you added an action part (in its properties panel). So if you want to add one of the custom action parts to your action and you have the action part selection dialog pop up by default, select some random action part first and change its type afterwards.

Members of the Visionaire community shared some of the plugins they developed. You can [[Action Part Plugins|download them from this wiki]].

== Installation of plugins ==

# Get the plugin zip file (either download one or develop/create your own).
# In your project root folder (where the .ved is) add a folder called "plugins", if there isn't already one.
# Unzip the downloaded plugin file and copy the folder from it into the "plugins" folder.
# Open your project in Visionaire and click the jigsaw icon in the upper right.
# The list of available plugins opens up. Click "Install" next to the newly added entry.
# Save your project.

== Develop a plugin ==

tbd

@@ Line 4: / Line 4: @@
 Plugins get installed per project, so when starting a new project you have to install plugins you wish to use (again), even if you used them before in another project. Open the plugin section through the jigsaw icon in the toolbar to see all plugins currently installed or ready to get installed. You can uninstall them here, too, of course.
-Once you have installed a plugin you are ready to use the newly added action part(s). You will find these custom action parts in the "Custom" section of the action part selection dialog and at the the bottom of the action part list in the action part properties panel.
+Once you have installed a plugin you are ready to use the newly added action part(s). You will find these custom action parts in the "Custom" section of the action part selection dialog and at the bottom of the action part list in the action part properties panel.
 Members of the Visionaire community shared some of the plugins they developed. You can [[Action Part Plugins|download them from this wiki]].

@@ Line 383: / Line 383: @@
 | text (str)
 | Field name in the editor
-| rowspan="2" | If you use this field for linking an object ("use=4" or "use=5"), be aware that you'll get a tuple string you have to convert into a link in ''player.lua'' by yourself. For example, a string of "(4,1)" stands for a link to the scene with id=1 ("4" is the scenes table).
+| rowspan="2" | If you use this field for linking an object ("use=4" or "use=5"), be aware that you'll get a tuple string you have to convert into a link in ''player.lua'' by yourself. Use <code>getObject(actionPart.String)</code> to get the object.
 |-
 | use (int)

@@ Line 313: / Line 313: @@
 | text (str)
 | Field name in the editor
-| rowspan="6" | If you want to use this field, you have to set "use=2" or "use=3" for the ''Integers'' field.
+| rowspan="6" | If you want to use this field, you have to set "use=3" for the ''Integers'' field.
 |-
 | control (int)

@@ Line 262: / Line 262: @@
 |-
 | rowspan="4" | <span class="inlinecode">integers</span>
-| rowspan="4" |
+| rowspan="4" | actionPart.Int (x)
 | use (int)
 | This either defines how many of the following integer fields to use – or it turns the ''integers'' field into a position picker.
@@ Line 269: / Line 270: @@
 * 2: Use the ''integer1'' field only
 * 3: Use the ''integer1'' and the ''integer2'' field
-| rowspan="4" |
+| rowspan="4" | If you use this field as a position picker ("use=1"), the x and y coordinates are passed over as two separate values ''Int'' and ''AltInt''.
 |-
 | useint3 (bool)

← Older revision		Revision as of 10:15, 24 February 2023
Line 19:		Line 19:
	== Develop a plugin ==		== Develop a plugin ==

−	tbd	+	<abbr title="to be done">tbd</abbr>
		+	{{toc}}