Cabbage Logo
Back to Cabbage Site

Edit mode destroys source code (Windows 10/11)

#4

Iā€™ve experienced this many times, and have stopped using the Edit mode because of this. Only using bounds() at the moment.

IMO, the Cabbage-section should be as strict as Csound when detecting syntax errors, but @rorywalsh might disagree :see_no_evil:

#5

Could nail the problem down a bit. Started with a new project, added some code and when I added this, the problem occured:

#define SLIDER1 textColour (  0,   0,   0), trackerColour (170, 170, 170)    
rslider  $SLIDER1 bounds ( 12, 14, 105,  101), channel ("att"),   range (0.01, 20, 1,   1,   0.01),  text ("Attack")

Same situation with this:

#define COMBO1  colour     (170, 170, 170), fontColour    (0,     0,   0)
combobox $COMBO1  bounds ( 20, 160, 200,  30), channel ("pol"),   items("0", "2", "4", "6"), text ("Off", "2", "4", "6"), value(1)

Even if I remove the #define (i.e. use the default colours), the problem persists. Something wrong with the rslider or combobox definition?

On the other side - this works fine:

#define LABEL1  textColour (  0,   0,   0), fontColour    (0,     0,   0)
label   $LABEL1  bounds(50, 164, 250, 30), text    ("HPF Filter Poles:")
#6

I am seeing the same destructive behaviour using curly brackets to create groups, the following gets destroyed badly when trying to move things:

image bounds (0, 0, 270, 170)
{
    image bounds(10, 10, 250, 50) colour(0, 255, 255, 255)
    {
        hslider bounds(0, 10, 240, 50) channel("band") range(0.0010, 1.5, .17, 1, 0.001) align("top") 
        label bounds(0, -8, 250, 30) text("FREQ SPREAD") fontSize(12) align ("centre")
        label bounds(0, 10, 250, 20) text("Focused <-------------------> Diffuse") fontSize(10) align ("centre")
    }
    image bounds(10, 60, 250, 50) colour(100, 255, 255, 255)
    {
        hslider bounds(0, 10, 240, 50) channel("dur") range(0.01, 2.5, 0.17, 1, 0.001)
        label bounds(0, -8, 250, 30) text("DURATION") fontSize(12) align ("centre")
        label bounds(0, 10, 250, 20) text("Short <-------------------> Long") fontSize(10) align ("centre")
    }
    image bounds(10, 110, 250, 50) colour(200, 255, 255, 255)
    {
        hslider bounds(0, 10, 250, 50) channel("rate") range(0.1, 2, 0.17, 1, 0.001)
        label bounds(0, -8, 250, 30) text("RATE") fontSize(12) align ("centre")
        label bounds(0, 10, 250, 20) text("Fast <-------------------> Slow") fontSize(10) align ("centre")
    }
}
#7

Thanks guys Iā€™ll take a look when I get a chance :+1:

1 Like
#8

Hi @stefanv, Iā€™m jut getting around to looking at this now. I donā€™t doubt that there is a problem here but I canā€™t seem to recreate it. Check the screengrab below. Note I obviously have to hit save after I enter the text in order to make it appear.

Would you mind posting a video, or explicitly outlining the steps I need to take in order to recreate the problem. Thanks.

#9

I just noticed now that you have sub groups in this. The dynamic syntax system was never really designed to handle this kind of complexity. :frowning:

#10

Any chance you could describe to me the simplest way I can recreate the problem on my end?

#11

I use curly brackets (Plants), with a label as the container, and with slider inside. Try to move the widget in GUI-editor with this example. It will do all sorts of odd stuff.

<Cabbage>
form caption("Untitled") size(400, 300), guiMode("queue"), pluginId("def1")
keyboard bounds(8, 158, 381, 95)
 
label bounds(0, 78, 80, 16) channel("label10002") {
    rslider channel("rslider10001") channel("rslider10001") range(0, 1, 0, 1, 0.001)
}
</Cabbage>
<CsoundSynthesizer>
<CsOptions>
-n -d -+rtmidi=NULL -M0 --midi-key-cps=4 --midi-velocity-amp=5
</CsOptions>
<CsInstruments>
; Initialize the global variables. 
ksmps = 32
nchnls = 2
0dbfs = 1

;instrument will be triggered by keyboard widget
instr 1
kEnv madsr .1, .2, .6, .4
aOut vco2 p5, p4
outs aOut*kEnv, aOut*kEnv
endin

</CsInstruments>
<CsScore>
;causes Csound to run for about 7000 years...
f0 z
</CsScore>
</CsoundSynthesizer>
#12

Yup, that does the trick alright :rofl: this isnā€™t going to be easy but Iā€™ll try to find a fix for it.

#13

What I do, is very simple:

  1. open a new file
  2. add ā€œsize(600, 500), colour(200, 200, 200), textColour (0,0,0)ā€ to the caption
  3. add the following lines to the cabbage part:
    #define SLIDER1 textColour ( 0, 0, 0), trackerColour (170, 170, 170)
    #define LABEL1 textColour ( 0, 0, 0), fontColour (0, 0, 0)
    #define COMBO1 colour (170, 170, 170), fontColour (0, 0, 0)
    rslider $SLIDER1 bounds ( 12, 14, 105, 101), channel (ā€œattā€), range (0, 20, 0.1, 1, 0.01), text (ā€œAttackā€)
    rslider $SLIDER1 bounds (114, 14, 105, 101), channel (ā€œdecā€), range (0, 20, 0.5, 1, 0.01), text (ā€œDecayā€)
    rslider $SLIDER1 bounds (218, 14, 105, 101), channel (ā€œsusā€), range (0, 1, 0.5, 0.5, 0.01), text (ā€œSustainā€)
    rslider $SLIDER1 bounds (322, 14, 105, 101), channel (ā€œrelā€), range (0, 20, 0.7, 1, 0.01), text (ā€œReleaseā€)
  4. say ā€œRunā€ to bring the GUI up
  5. say ā€œStopā€
  6. enter edit mode
  7. move a slider.

Result: garbage.

Thatā€™s all.

1 Like
#14

Two things here seems to break things. 1) The tab indentation, and 2) the fact you have no bounds set for the label.

#15

I canā€™t seem to recreate this here? Can you spot anything Iā€™m not doing? It does add a few colour identifiers, but thatā€™s not so bad.

#16

Very strangeā€¦

I used the built-in windows recorder, so I can show only the cabbage window, not the pluginā€¦

ā€¦and now the video is too big. Pls. find the link to the video here (valid for one week):

#17

Thanks @stefanv, can you remove the tabs at the start of each line and try again?

#18

Great - that does the trick! Problem solved!!!

(But does not improve raedabilityā€¦ :frowning: )

#19

No, but at least we know now what is causing the issue. I have some place to start :slight_smile:

1 Like
#20

I pushed a fix for this now. While some of the use cases above still result in issues (1, 2), adding spaces or tabs to the starts of lines in order to create a better formatted document should no longer results in garbage. :+1: So @stefanv, you should be free to add as many tabs/spaces as you like from now on.

2 Likes
#21

Tested and approved. Thanks very much!

1 Like
#22

Which version should I use for this fix?

I got the same problem on Mac, Cabbage 2.9.

https://recordit.co/ZqWYqP7dUa

What I did was basically replacing my existing section with the one from the tutorial here: https://cabbageaudio.com/docs/using_imgs/

#23

Hey @strongbear, welcome to the forum. Whenever you hit an issue like this the first thing you should do is install the latest development build. You can read about how to access them from here. If that doesnā€™t help let me know :slight_smile: