@DanH Does this help?

https://docs.hise.dev/scripting/scripting-api/content/index.html#setusehighresolutionforpanels

@pelle How do you know it stopped compiling?

@inlandempire Yeah, if you bought Logic at any time in the past you'll be able to download the latest version from your Apple account in the App Store on Mac. Free lifetime updates!

Not sure about the loop points, but I'd be surprised if HISE doesn't already support Logic loop points. And if it doesn't, it needs to because I'll be doing some sample-based plugins soon!

@inlandempire If you happen to be on Mac, I find Auto Sampler (part of Logic and Main Stage) to be way better than Sample Robot for recording and editing multi-samples.

If you don't have Logic, or don't want to buy it, then Main Stage is only about $50/£30 and I'm pretty sure it has the same full Sampler/Auto Sampler features as Logic.

@Christoph-Hart I've never told Cursor/Claude to match existing code styles and it seems to do a pretty good job.

Except it litters whitespace all over every empty line

But your guidance files will be valuable because I won't have to pretend I know what good C++ looks like!

@David-Healey This fixes it for me, but it needs testing in a real project:

https://github.com/christophhart/HISE/pull/891

@David-Healey HISE master - do you know something I don't?

@Christoph-Hart said in New LAF Properties for Modulation Display: Selected Source vs Accumulated Range:

that's precisely the difference between "lol AI cannot do s***" and "boy we're f***ed"....

1,000% this

@Christoph-Hart It would indeed!

@Christoph-Hart said in CSS Errors for every component:

TLDR: Easy fix: add *{} at the top of your stylesheet

To the top of every stylesheet defined in the code?

I have a lot of small stylesheets like this:

lafCredits.setInlineStyleSheet("
label {
    color: #ccc;
    font-family: 'Barlow';
    font-size: 17px;
    letter-spacing: 0.05em;
    text-align: left;
}");

@DanH Interesting. Still, must be related to this my issue I guess:

https://forum.hise.audio/topic/14421/css-errors-for-every-component

Since the Jan 25th CSS updates, I'm seeing a large amount of CSS Error lines in the console when I load the plugin XML.

Interface:! CSS Error: can't find CSS for component btnIconPrev
Interface: 	Use one of these CSS selectors to define a stylesheet for the base component: 
Interface: 	.scriptbutton
Interface: 	#btnIconPrev
Interface: 	button
Interface: 	*

One of these blocks for every component, plus the whole list repeats twice. So for my small plugin I see 442 lines of these errors when I load my plugin.

Is this expected?

@DanH Do you also see a large amount of CSS Error lines in the console with you load your plugin XML?

@Christoph-Hart Nice!

Does a new issue automatically trigger the workflow?

@Lindon I imagined 10+ years of HISE development would've taught you "I know exactly how all this sh*t works". It's all just apps, code directories and config paths at the end of the day.

Although I suppose if all versions of the HSIE app reference the same Application Support files then it could get messy.

OK, I concede!

@Lindon Unless I'm misunderstanding, none of the HISE versions require you to install VS2026.

And I don't understand why you can't have both VS2022 and VS2026 installed, along with 2 versions of HISE (latest version and older version for your older project) with and 2 copies of the source code.

I know we tell beginners to only have one version of HISE but I'm sure you know enough about all this to make sure each version of HISE references the correct source code and VS version.

@DanH I use Claude Opus and Sonnet in the Cursor IDE (desktop app) with he whole HISE repo and it work great.

Cursor is good about sending the right amount of context and caching where it can.

@David-Healey

@PV3679 Ideally you'd only have one copy of the HISE source on your machine.

Also, it might work better if the source is on the C: drive.

Last thing - are you on the latest develop commit, with JUCE as a git submodule?

@Christoph-Hart

Maybe the 32GB RAM on my MacBook Air means there's enough to go around so it's not like typing through syrup.

I interact with Xcode, and now Visual Studio, as little as possible anyway. Launch, press Build keyboard shortcut, wait, quit.