HISE Logo Forum
    • Categories
    • Register
    • Login

    Modulation Matrix header and plotter CSS

    Scheduled Pinned Locked Moved Solved General Questions
    4 Posts 2 Posters 332 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.
    • ustkU
      ustk
      last edited by ustk

      Header

      When setting different widths for the components, like in this case the button (40px while sliders and CBs are 75px) the columns don't reflect the real width. See the header distribution pushing the other labels:

      Screenshot 2025-09-01 at 15.47.49.png

      Is there a way to distribute the different widths, or have column selector?

      td, .targetLabel
      {
      	color: #999;
      	font-size: 10px;
      	width: 75px; /* all columns set to 75px despite the button is needing 40px */
      }
      

      Plotter

      As for the plotter, it doesn't seem to react to any CSS (background, color, etc...)

      Hise made me an F5 dude, browser just suffers...

      Christoph HartC 1 Reply Last reply Reply Quote 1
      • Christoph HartC
        Christoph Hart @ustk
        last edited by

        @ustk you can address the columns using the id selector - the id selector for each column is assigned to both header and items in each row so it will affect the entire column - this is explicitly designed like this for this very use case:

        #sourceindex, #targetid
        {
        	display: none;
        }
        
        #mode
        {
        	width: 200px;
        }
        
        #inverted
        {
        	width: 10%;
        }
        
        #plotter
        {
        	/** the plotter has the flex-grow property set to fill the remaining width so if we want to set it, we need to reset that first. */
        	flex-grow: 0; 
        	width: 50px;
        	background: red;
        }
        

        And yes I've deliberately left out the plotter from CSS - the reason is that it has to convert the realtime updated path to a base64 string, pass that to the css renderer to be converted back to a path and this imposes significant CPU overhead for complex paths that are updated with ~30fps.

        ustkU 1 Reply Last reply Reply Quote 1
        • ustkU
          ustk @Christoph Hart
          last edited by

          @Christoph-Hart Oh nice! I was sure I tested that but I've necessarily made a mistake otherwise it wouldn't have been a nice day ☺

          Hmmm... Understandable for the plotter, but would there be a way to still customise it behind the scene so the CSS renderer hasn't to take care of it?

          Hise made me an F5 dude, browser just suffers...

          Christoph HartC 1 Reply Last reply Reply Quote 0
          • Christoph HartC
            Christoph Hart @ustk
            last edited by

            @ustk sure you can use a laf script function as always.

            1 Reply Last reply Reply Quote 1
            • ustkU ustk marked this topic as a question
            • ustkU ustk has marked this topic as solved
            • First post
              Last post

            10

            Online

            1.9k

            Users

            12.4k

            Topics

            108.3k

            Posts