-
Notifications
You must be signed in to change notification settings - Fork 2
Home
LeonaMorro edited this page Jan 29, 2017
·
18 revisions
All documentation here applies to the latest version of nPose 3.0 and beyond.
- uses only one notecard type:
SET. TheBTNandDEFAULTNotecards are no longer necessary (and are marked as deprecated) - you can define your own text in the menu prompt. See [MENUPROMT](NC Contents#menuprompt)
- Buttons/Path (NC names) may contain non-ASCII characters (workaround for the LL restriction) see NC Names
- Buttons/Path (NC names) may contain comments (usable for Button sorting (and more)) see NC Names
- Buttons/Path/ButtonPermissions (NC names) may contain macros (shortcuts) see NC Names
- No need for a "-" sign at the end of the Button name
- a new notecard called
.initthat will run once after a script reset (to set initial values) see NC Names - an API for (Menu-)Plugins TODO:DESCRIPTION
- some new commands: [DEFAULTCARD](NC Contents#defaultcard), [OPTION]((NC Contents#option), [UDPBOOL](NC Contents#udpbool), [UDPLIST](NC Contents#udplist), [MACRO](NC Contents#macro), [PLUGINMENU](NC Contents#pluginmenu), [MENUPROMPT](NC Contents#menuprompt), [PLUGINCOMMAND](NC Contents#plugincommand)
- a revamped changeSeat/unsit dialog (implemented as menu plugin) with some options like grouping, changing only to not occupied seats and more
- removed the code for the admin menu (you may use the provided Utility NCs to build your own)
- rewritten
nPose SAT-NOTSAT handler. It may be used to send some other generic events in addition to the (NOT)SATMSGs. - a few more tweaks in the representation of a menu
No. We provide an tool called UpdateTool nPose 2 to nPose 3 that should help you with the upgrade process.
If you are currently satisfied with your nPose 2 object there is no need to upgrade to nPose 3. We will do bug fixing in nPose 2. But don't expect any new features for nPose 2.
- if you use nPose only to play your 300+ animations, then stay with nPose 2.
- in nPose 3 Menus will have a noticeable slower response time. This is per design. If you can't accept that, then stay with nPose 2.
- nPose 2 is stable and mature. Backward compatibility was always high priority. With nPose 3 we want to go a more progressive way. If you can't accept that, then stay with nPose 2.
In all other cases: Of course! Use it.
-
Getting started
-
Reference
-
Changelogs
-
Internals