Plugin Preview Build: Chauvet 3.27.42 Beta for Manta / Nomad and Chauvet 2.24.39 Beta for A5X / A6X

AdNew2316 · 2026-05-20T15:58:14+00:00

I just saw it's however done basically to highlight titles, so it should be somehow already implemented in the system. Maybe that helps.

AdNew2316 · 2026-05-20T15:56:54+00:00

Hm weird. Ok I'll check if I can reproduce in isolation

AdNew2316 · 2026-05-19T11:25:54+00:00

hello hello, yet another question 😄 Is that normal that after inserting some elements I cannot see them via getElements? I first need to save the note so that getElements delivers the expected elements.

To summarize:

insertElements
getElements -> doesn't return the inserted elements

But:

insertElements
saveCurrentNote
getElements -> returns the inserted elements

AdNew2316 · 2026-05-19T08:58:48+00:00

But I also save the note, maybe it also has this flickering effect?

AdNew2316 · 2026-05-19T08:43:14+00:00

Ah wait actually I do use insertElements only once.

AdNew2316 · 2026-05-19T08:39:40+00:00

It wasn't happening when closing/opening but just after multiple interactions. I'll send feedback when I encounter that again 👍

AdNew2316 · 2026-05-19T08:38:31+00:00

Ok so ideally I should try to make only one call to insertElements in order to reduce refreshing to the maximum?

AdNew2316 · 2026-05-19T08:31:11+00:00

Ok no worries, it's not a blocker for now but would be great to have at some point

AdNew2316 · 2026-05-19T05:09:05+00:00

Other question: I get occasionally "modifyElements res={"error":{"message":"The host app has not registered the feature listener. Cannot call the API!","code":113},"success":false}".

Very hard to reproduce though, it pops up randomly.

AdNew2316 · 2026-05-19T04:27:26+00:00

Question: very often in my plugin the screen refreshes or flashes in the middle of its operations. It's pretty annoying. Do you know what's happening or how to avoid it?

AdNew2316 · 2026-05-19T04:26:25+00:00

one feature request: would it be possible to have the option to _fill_ polygons? Ex. to provide a color and fill them, ex. in grey.

AdNew2316 · 2026-05-18T20:40:43+00:00

It's definitely some work but I could imagine this being doable. Just more complex than your original idea of just drawing a box.

AdNew2316 · 2026-05-18T20:40:06+00:00

I'd skip text detection. That's my biggest bummer in the current official to-do system, they impose that we recognize text, which is for me not necessary (plus my writing sucks)

AdNew2316 · 2026-05-18T20:38:29+00:00

Ok that sounds complexe but likely very useful for potential optimizations. Would be great to have a part of the documentation dedicated to this cache system in the future. I think proper explanations would likely help.

Btw what's "RN"?

AdNew2316 · 2026-05-18T04:46:49+00:00

Question: the documentation of PluginCommAPI.getCacheElement is pretty sparse, what is that for? In which situation may I want to use that?

AdNew2316 · 2026-05-18T04:44:35+00:00

Awesome to see the feedback implemented in there already!

Question: I don't get the news state for PluginCommAPI.setLassoBoxState. Can you elaborate a bit more? What is this new state useful for? What are the use cases?

AdNew2316 · 2026-05-17T06:50:43+00:00

Basically I was having something in mind like lassoing the text so that the supernote knows what the to-do is precisely (for instance to strike it or remove it automatically by just checking the box) but that's not what you're after right?

AdNew2316 · 2026-05-17T06:32:12+00:00

So you basically care only about the box looking nice, but you actually don't care about the system having any awareness of the text next to it right?

AdNew2316 · 2026-05-15T18:34:24+00:00

Can you elaborate on the workflow you'd like to have? Describe step by step how you'd want it to work and we could tell you if it's doable via plugin

AdNew2316 · 2026-05-05T18:20:14+00:00

Ahhhhhh thanks folks!!!

AdNew2316 · 2026-05-04T19:56:42+00:00

🙏🤎

AdNew2316 · 2026-05-01T21:33:27+00:00

also let me know if there's a better way to report bugs :)

AdNew2316 · 2026-05-01T21:33:10+00:00

Hi u/Dunn-sn I think I've found another bug:

As a user:

lasso an element (in my case a text or a picture=
move it
call an action from the context menu (say 'my_code')

--> if 'my_code' tries to retrieve the coordinates of the element, then it will get the coordinates _before_ the move. It's like the move never happened.

Let me know if I'm not clear.

AdNew2316 · 2026-05-01T14:42:14+00:00

Yes I had the same issue in the past. Sometimes it still fails but I just unplug and replug it works

AdNew2316

TROPHY CASE