Forum
    • Categories
    • Register
    • Login

    Multiple Styles for Controls?

    Scheduled Pinned Locked Moved Scripting
    11 Posts 5 Posters 77 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ChazroxC
      Chazrox @bwoogie
      last edited by

      @bwoogie You could create an array of selected components and just apply its own laf functions to them. You could make how ever many different lafs you want. Make sure you're using LocalLookAndFeel as opposed to GlobalLookAndFeel. Does that answer your question? I think im understanding what you're asking.

      B 1 Reply Last reply Reply Quote 0
      • B
        bwoogie @Chazrox
        last edited by

        @Chazrox Yes, that makes sense. That may be the way I'll do it, if a better way doesn't show up. I'd prefer to be able to just change a style setting in the gui editor - like how you'd choose a knob or a slider. But at least I'll have a method.

        ChazroxC David HealeyD dannytaurusD 3 Replies Last reply Reply Quote 0
        • ChazroxC
          Chazrox @bwoogie
          last edited by

          @bwoogie The only way I think you can change the actual style of the knob/button like that (and we're not just talking about colour and dimensions right?), you can use filmstrip images and just load different ones through the property editor. Then you can change the images individually.

          1 Reply Last reply Reply Quote 0
          • David HealeyD
            David Healey @bwoogie
            last edited by

            @bwoogie use local look and feel instead of global.

            Free HISE Bootcamp Full Course for beginners.
            YouTube Channel - Public HISE tutorials
            My Patreon - HISE tutorials

            1 Reply Last reply Reply Quote 1
            • dannytaurusD
              dannytaurus @bwoogie
              last edited by dannytaurus

              @bwoogie The way to make your code reusable is LocalLookAndFeel in an external script.

              Create multiple LAFs, one for each control style, then apply them to different controls based on their ID. If you stick to a convention of IDs it's very quick and easy. Something like:

              Prefix with knbSm for small knob style:
              knbSmOctave
              knbSmTune

              Prefix with knbLg for large knob style:
              knbLgFreq
              knbLgRes

              Then create and apply your LAFs like this:

              // Small Knobs
              const lafknbSm = Content.createLocalLookAndFeel();
              
              lafknbSm.registerFunction("drawRotarySlider", function(g, obj)
              {
                // draw your small knob graphics here
              }
              
              for (knob in Content.getAllComponents("knbSm")) knob.setLocalLookAndFeel(lafknbSm);
              
              // Large Knobs
              const lafknbLg = Content.createLocalLookAndFeel();
              
              lafknbLg.registerFunction("drawRotarySlider", function(g, obj)
              {
                // draw your large knob graphics here
              }
              
              for (knob in Content.getAllComponents("knbLg")) knob.setLocalLookAndFeel(lafknbLg);
              
              

              To make it reusable between plugins, move all your LAF code to an external JS file and include it in the main interface script like this:

              include("LookAndFeel.js");

              Then you just copy that file to the Scripts folder of a new project and include.

              Meat Beats: https://meatbeats.com
              Klippr Video: https://klippr.video

              LindonL 1 Reply Last reply Reply Quote 1
              • LindonL
                Lindon @dannytaurus
                last edited by Lindon

                @dannytaurus said in Multiple Styles for Controls?:

                Create multiple LAFs, one for each control style, then apply them to different controls based on their ID. If you stick to a convention of IDs it's very quick and easy.

                ..this works but I do something a bit more flexible, for buttons at least - I use the text area to define the style...

                so the json for a button I want to have the "Flat style" looks like this:

                [
                  {
                    "type": "ScriptButton",
                    "id": "PadEditSelector",
                    "x": 170.0,
                    "y": 30.0,
                    "parentComponent": "EditPanel",
                    "radioGroup": 51.0,
                    "text": "FLAT:Edit Pad"
                  }
                ]
                

                ..and in the interface looks like this

                11714093-c128-42ef-b199-d85704a925f5-image.png

                There's a giant loop thru all components in theLAF.js and the relevant bit is:

                
                	
                const var allComponents = Content.getAllComponents("");	
                
                
                for (c in allComponents)
                {	
                
                	if(c.get("text").contains("FLAT"))
                	{
                			c.setLocalLookAndFeel(flatButtonLAF);
                			continue;
                	};
                
                }	
                

                and the LAF itself looks like this:

                const var flatButtonLAF = Content.createLocalLookAndFeel();
                
                flatButtonLAF.registerFunction("drawToggleButton", function(g, obj)
                {  
                	var a = obj.area;
                	g.setFont(SkinSpace.skin.stdFont, 16);
                	// get the text out..
                	var ffText = obj.text;
                	var fftextStart = ffText.indexOf(":");
                	ffText = ffText.substring(fftextStart+1,ffText.length);
                	
                	//Console.print("drawing flat:" + ffText);
                	var fillColour = SkinSpace.skin.highlight;
                	var TextOnColour = SkinSpace.skin.outline;
                	var hoverOnColour;
                	
                	//var cThisColour;
                	if(obj.value)
                	{
                		g.setColour(fillColour);
                		g.fillRoundedRectangle(a, 0);
                		g.setColour(SkinSpace.skin.highlightContrast);
                	}else{
                		g.setColour(SkinSpace.skin.stdText);
                	}
                	
                	if(obj.over)
                	{
                		g.setColour(SkinSpace.skin.Over);
                		g.fillRoundedRectangle(a, 0);	
                		g.setColour(SkinSpace.skin.highlightContrast);
                	};
                	//g.setColour(SkinSpace.skin.stdText);
                	g.drawAlignedText(ffText, [a[0],a[1],a[2],a[3]], "centred");
                
                });
                

                ..it uses a skin file to set the colours...

                HISE Development for hire.
                www.channelrobot.com

                dannytaurusD 2 Replies Last reply Reply Quote 0
                • dannytaurusD
                  dannytaurus @Lindon
                  last edited by

                  @Lindon Nice.

                  Incidentally, radio group 51? What the hell are you building?! 😂

                  Meat Beats: https://meatbeats.com
                  Klippr Video: https://klippr.video

                  1 Reply Last reply Reply Quote 2
                  • dannytaurusD
                    dannytaurus @Lindon
                    last edited by

                    @Lindon You could simplify the control text a bit:

                    // Simplify this:
                    var ffText = obj.text;
                    var fftextStart = ffText.indexOf(":");
                    ffText = ffText.substring(fftextStart+1,ffText.length);
                    g.drawAlignedText(ffText, [a[0],a[1],a[2],a[3]], "centred");
                    
                    // to this:
                    g.drawAlignedText(ojb.text.split(":")[1], [a[0],a[1],a[2],a[3]], "centred");
                    

                    This assumes you'll always have the ":" in the obj.text. If not, the short version blows up.

                    Meat Beats: https://meatbeats.com
                    Klippr Video: https://klippr.video

                    1 Reply Last reply Reply Quote 0
                    • B
                      bwoogie
                      last edited by

                      Thanks guys! I realized i should be using LOCAL Look and Feel before I even got out of bed this morning 😆

                      ChazroxC 1 Reply Last reply Reply Quote 3
                      • ChazroxC
                        Chazrox @bwoogie
                        last edited by

                        @bwoogie and when you're done with that....🤣

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post

                        30

                        Online

                        2.1k

                        Users

                        13.0k

                        Topics

                        112.5k

                        Posts