However, the libPlasma editing is not for the faint of heart. You need to create the GUI button from scratch (or rather copy and modify it from one of Cyan's GUIs). I also made a feeble attempt to implement pfGUIButtonMod into PyPRP but unfortunately I failed miserably.
The good news is that you do not need the GUI button. It is only used to exit the GUI, but you can do that by hitting escape instead. So I would say this is usable as it is.
One more thing: you also need a clickable to activate the GUI. This clickable must be a different object than the GUI, although it can be a duplicate of it. Then you hide the GUI plane itself somewhere underground or behind a wall. The clickable requires the following AlcScript:
- Code: Select all
<clickable object>:
logic:
modifiers:
- tag: ModDialog
cursor: poised
flags:
- localelement
activators:
- type: objectinvolume
remote: <click region>
triggers:
- any
conditions:
- type: activator
activators:
- type: picking
- type: objectinbox
satisfied: true
actions:
- type: pythonfile
ref: $PythDialog
actions:
- type: pythonfile
tag: PythDialog
pythonfile:
file: xDialogToggle
parameters:
- type: activator
ref: logicmod:$ModDialog
- type: skip
- type: skip
- type: string
value: Plane1
...assuming that your GUI dialog is called Plane1 as in GPNMilano's example. The Python file we are using is a global one. So no need to worry about creating it.