getLuaBounds error in 1217

[dasfaker]

I’m getting an error with this command:

ani_mod = panel:getModulatorByName(“LCD Info Text”):getComponent():getLuaBounds()

“attempt to call method ‘getLuaBounds’ (a nil value)”

[atom]

Good catch i missed something, i’ll post a fix later today.

 

Also you can also and you should use, the normal JUCE calls to a component:

button = panel:getComponent("button")
rect = button:getBounds()
console("COORDS: "..rect:toString())


COORDS: 144 128 48 70

So instead of using the old deprecated CtrlrLuaRectangle class you just use a normal Rectangle class from JUCE and all method of that class are available in the “rect” object.

But the old methods must work too for compatibility reasons, i will fix it

• This reply was modified 11 years, 4 months ago by atom.
• This reply was modified 11 years, 4 months ago by atom.

[TK.]

mod:getX() doesn’t work anymore – is this compatibility issue really intended?
Best Regards, Thorsten.

[atom]

What’s “mod” in this case ? a modulator or a component ?

just to update:
it’s the same bug, inheritance issue the class you are getting should be a CtrlrComponent that’s a subclass of Component, instead you just get Component. I already fixed that in the source, the nightly will have a fix for it.

• This reply was modified 11 years, 4 months ago by atom.

[TK.]

Yes, a modulator, and it still fails with r1218

I strongly recommend you to use the latest MBSID panel for testing purposes before doing any release (even nightlies): http://midibox.org/forums/topic/16709-ctrlr-based-editor-for-mbsid-v2/

to ensure that you won’t run into compatibility issues again.
Not at least I recommend it, because you own a MBSID as well, which means that you are able to test all transactions! 🙂

Best Regards, Thorsten.

• This reply was modified 11 years, 4 months ago by TK..

[atom]

Damn, i never finished my unit 🙂 but i promise to test the next nightlies with your panel and some 2 others. But a modulator never had a getX() method a component did.

[TK.]

It was your proposal to program the rotation stuff this way – now it’s your issue! 😉

Best Regards, Thorsten.

[atom]

If the .bpanelz loads and i can move stuff around is it enough for a test ? Maybe you can tell me what sort of a test scenario to do, remember my MBSID is not working 🙂

[TK.]

Yes, a simplified test procedure would be sufficient. All Lua incompatibility issues that I had in the past can be reproduced by loading the panel and moving one of the oscillator or filter faders.
SysEx messages should be sent, and you should never see a Lua error message.

Best Regards, Thorsten.

 

[atom]

Well then the latest nightly passed that test.

[dasfaker]

I just changed all animation code because it was no longer working, I was getting the same Lua errors (so no compatibility with previous code yet in 1220). I’ve followed the example animation panel and now I have its working fine.

[atom]

Tehre is a new RENDERING demo, it will show almost all possibile graphics related stuff. it’s not anywhere near ready but just a reminder that it’s there and when in doubt look at it.

[dasfaker]

Wow, this demo looks very promising!!

[atom]

My goal is to re-create the Rendering component in Juce Demo application (i attached a windows binary for those of you that are lazy and don’t care). I want to do this so first of all i can see that all the graphic/drawing classes are there, and second and more important i need to optimize my code for that rendering process to be as fast as possible and there is a lot ways optimizations can be done, the most important one is LUA and it’s mechanisms.

Anyway it’s a debugging panel for me. I hope to finish it soon.

Attachments:

You must be logged in to view attached files.

[Author]

Posts