resize in presentation mode, more robust initialization, performance improvement, small bug fixes
This commit is contained in:
18
README.md
18
README.md
@@ -3,9 +3,10 @@
|
||||
A [jsui] replacement for the [preset] object in Cycling'74 Max.
|
||||
|
||||
## Features
|
||||
- Same click + modifier key behavior as the vanilla object to store and delete presets
|
||||
- Drag and drop presets to re-organize
|
||||
- Display presets as a grid or a list
|
||||
- Scrollable (requires Max 8.6.2)
|
||||
- Scrollable list layout (requires Max 8.6.2)
|
||||
- Shows active preset even if recalled directly from pattrstorage
|
||||
- Shows previously active preset, with the ability to ignore preset 0 if it being used as an intermediary step
|
||||
- Shows presets being interpolated (using recall or recallmulti)
|
||||
@@ -14,24 +15,27 @@ A [jsui] replacement for the [preset] object in Cycling'74 Max.
|
||||
- Ability to rewrite json file automatically every time a preset is stored/moved/deleted/renamed/(un)locked
|
||||
- Helps keeping in sync a umenu with the list of stored slotstlet
|
||||
- More look customization
|
||||
- Same click + modifier key behavior as the vanilla object to store or delete presets
|
||||
- Dynamically adapts to resize both in Edit and Presentation mode
|
||||
- Select mode: simple click selects the slot, double click recalls it (allows for organizing presets without recalling them)
|
||||
- Color mode: ability to color sstored presets with 6 customizable colors (currently colors are only assigned automatically depending on slot number)
|
||||
|
||||
|
||||
## How to use
|
||||
- Place `tc.preset.js` in the same directory as your patch, or somewhere in the Max search path
|
||||
- Create a [`jsui @filename tc.preset.js`]. You can either add `@jsarguments` followed by the name of the pattrstorage you want to communicate with, or set that later by sending a `pattrstorage` (followed by the pattrstorage name) message to the [jsui].
|
||||
- Create a [`jsui @filename tc.preset.js`].
|
||||
- Connect the [pattrstorage] outlet to the [jsui] inlet
|
||||
- Set the jsui attribute named "pattrstorage" to the name of the pattrstorage you just connected (or send a message like "pattrstorage my_pattrstorage_name")
|
||||
|
||||
|
||||
## Limitations
|
||||
- Resize doesn't work in Presentation mode (jsui limitation)
|
||||
- Due to the way [pattrstorage] works, some pattrstorage-specific messages should be sent to the [jsui] instead of the [pattrstorage]. Some to both:
|
||||
- `recall`, `delete`: send to [pattrstorage] only
|
||||
- `recall`: send to [pattrstorage] only
|
||||
- `recallmulti`, `slotname`: send to [pattrstorage] first (for better timing), then to the [jsui]
|
||||
- `store`: send to [jsui] only
|
||||
- Some messages to pattrstorage causes the jsui to be out of sync (`clear`, `insert`, `lockall`, `read`, `readagain`, `remove`, `renumber`). If you use any of these messages, make sure to then send a `resync` to the jsui.
|
||||
- The js program send a lot of message to the [pattrstorage] (using `maxobj.message()`syntax, so without patch cord), which in return send (using a patch cord) a lot of messages required for the [jsui] to stay in sync. Using one of the above messages incorrectly, or sending `getslotlist`, `getslotnamelist`, or any message that will impact the presets might cause the [pattrstorage] to get out of sync. In case something like that happens, you can send the `resync` message to the [jsui].
|
||||
|
||||
## Desired features (for someday)
|
||||
- Select mode: simple click selects the slot, double click recalls it
|
||||
## Desired features (for someday, if ever)
|
||||
- No need for a patch cord (programmatically create a [send]/[receive] pair?)
|
||||
- Ability to lock/unlock and rename directly in the jsui without the need of external objects
|
||||
- Ability to target a [pattrstorage] in a different patcher level
|
||||
|
Reference in New Issue
Block a user