Cabbage2lite pre-testing: 1

[rorywalsh]

@t_grey

cabbage plugin name doesn’t appear in window title bar, just shows “CabbageLite”

Fixed. It was changing the name when opening manually, but not from the command line.

@t_grey

I can only have one C2 window open at a time (possibly due to how sublime hooks in for the console/debug output? didn’t test standalone yet), had no problems launching multiples from sublime with C1 tho.

OSX won’t let you launch 2 instances of a program unless you start them explicitly from the command line. This works. I just checked it. Not sure what kind of hoodoo you will need to use to sort this issue out. I’m also not sure why the same thing you did for C1 doesn’t work in this instance. There is very little different in the code.

@t_grey

single line groupbox with { } creates issue as mentioned before, even when not a plant or nested. I know it’s an easy fix on my end too, but as I update more of my old effects I really feel like this should behave the same between versions.

Can you explain it again I couldn’t find the thread from earlier..we have a bad habit of going off topic!

@t_grey

button size or font size is just barely different, a button that’s text displayed fine in c1 now shows “…”, very minor, but maybe worth knowing. example: button bounds(28, 55, 20, 18), text(“Inv”, “Inv”)

It’s known. The graphics code was completely rewritten. Some of the old code was erroneous. After updating it certain things look slightly different, but the upshot is the C++ code is better written and easier to maintain. If these thing get to you, it might be time to look at using your own GUI elements in the form of PNGs or SVGs.

@t_grey

floating point digits displayed in popuptext when range sets step size to 1 (rslider)… popup shows 1.00, 2.00, 3.00 etc.

Fixed in git.[quote=“t_grey, post:1, topic:777”]
gentable doesn’t respond to identchannel for tablecolour changes? didn’t try other fields like bounds yet
[/quote]

You need to use tablecolour:N(), where N is the table number, starting at 0 for the first table. This was change to allow both colour names and RGBA values for tables.

@t_grey

new hrange tabs are too easy to “miss” (maybe even invisible pixels?) and grab the width instead of the limit
hrange suffers large amounts of lag when grabbing full range to move. This was found on an effect I just dug out of the “basement” tho, it’s possible the problem is something I did dumb.

I haven’t checked these in a while. I can’t even grab full range to move. I’ll take a look. Drawing the actually thumbs for these sliders is a pain. Juce doesn’t come with such sliders so I’ve had to throw together my own. Hence the issues!

@t_grey

An rslider with range(0,0,0,1,.01) doesn’t render properly…

In debug mode this actually causes a JUCE assert. It’s not legal in JUCE to set up a slider this way. I think the fact that it doesn’t render properly is a good indication to the user that it’s a stupid idea? If you want a slider that doesn’t do anything set it to inactive?

@t_grey

Defines with similar names now behave differently! For example,

I think I know what’s going on there. I’ll take a look.

@t_grey

Lastly, purely aesthetic feedback… I feel like the new hrange tab style is really mismatched now when viewed next to hsliders.

See the note above. I can try to update the look a little, but these suckers aren’t easy to get right. The smaller the thumb is the harder it is to grab them, but the better it looks I’ll take another look..