CtrlrX v5.6.29 Release - GUI LookAndFeel_V4 Update #604
Replies: 12 comments 57 replies
-
|
// Reserved For Posting Links To Builds // CtrlrX 5.6.29 | macOS Intel versions : CtrlrX 5.6.29 | macOS Apple Silicon versions : CtrlrX 5.6.29 | Windows 10 |
Beta Was this translation helpful? Give feedback.
-
|
Incroyable! |
Beta Was this translation helpful? Give feedback.
-
|
As requested by @damiensellier here are the v5.6.29 zips for MacOS Silicon CtrlrX 5.6 29 Silicon Mac.app.zip |
Beta Was this translation helpful? Give feedback.
-
|
Those colourschemes, do they work for Lua-editor as well? That would be awesome because the v4 light scheme is just causing eye strain at 2 at night. Too bright. I can't test it myself, no mac-intel here. But I assume I can build a Windows version when I download your repository. What do you mean exactly by saying: Description/ID in the property pane switches without selecting other tabs to update it? To add to John: C'est incroyable n'est ce pas? C'est magnifique. Keep up the good work Damien!! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Yep all the windows in Ctrlr are following Juce colour schemes, not sure the LUA editor is going to turn "dark mode" though. I can do a custom option for that now that I know Ctrlr code by heart :) You know when you use to click the description / Id button, the result was not showing right away unless you select another component or another tab in the property pane to get it refreshed. Now it's fixed so you can see the right property ID for LUA instantly like this : |
Beta Was this translation helpful? Give feedback.
-
|
It's all good. I thought it had something to do with the ID's. I never noticed the problem because the ID's refresh if you do it from the Menubar (View -> Tick Property/ ID names, then click "Refresh property lists"). But it is cool to do it with just one tick box in the property panel, it's what the tick box is for, right? If I can find the time to do a Windows build without much hassle, I'll post it here. *Edit, I stated the problem wasn't present in the Windows version. It is present when you use the tickbox in the property panel. Puts head in shame. Didn't remember that tickbox was there, to be honest. Or I must have gotten used to the whole Menubar diving sequence to change the ID's into text. |
Beta Was this translation helpful? Give feedback.
-
|
@damiensellier Realy great work! I did a very quick test on my system and here are a few observations:
Again, these are just some brief observations and not such big deal. It's still a great work! |
Beta Was this translation helpful? Give feedback.
-
|
Sliders V1 V2 V3 have the same colour. V4 is slicker with the 4 palettes. |
Beta Was this translation helpful? Give feedback.
-
|
Fantastic job Damien! |
Beta Was this translation helpful? Give feedback.
-
|
@dobo365 Thanks! Alert windows and popup style will follow the LookAndFeel selected in the global properties. You'll get macOS alerts : |
Beta Was this translation helpful? Give feedback.
-
|
I noticed that Ctrlr freezes when exporting instance. I don't know if it is because of disk access limitation due to be an un-code-signed application. 
It's ugly but it doesn't freeze :) 
|
Beta Was this translation helpful? Give feedback.
-
|
After some build errors concerning some "copied over fancy tokens", probably some space or backslashes in CtrlrPanel.cpp, I was able to build and run CtrlrX. But as soon as I tried to change to "LookAndFeelV4 Dark", Ctrlr crashed. Reopening the panel reverts the LookAndFeel to V3, albeit in a dark mode. It does that with every possible action on that combobox to be exact, it's not just "that" option. Crash Report: But weird thing is, when I delete all the settings in appData, Ctrlr opens with LookAndFeel v4, like Ctrlr 5.6.23. But the look and feel is applied to sliders and so on. -- Also noticed that the color picker sometimes is "behind" the Ctrlr window. Looks like there is some "double click" going on that puts the Ctrlr Window in front of the Colour picker. To be more exact, looks like the ColourLabel is grabbing focus. panelPropertyDisplayIDs works as intended. Never noticed this but probably this is present in older Ctrlr versions as well: uiPanelPropertiesOnRight, the panelPropertyComponent IS on the right when the box is unticked. One would think it should be the other way around. Ticked = on the right. Unticked = on the left. The extra Component Mouse options are there for Sliders and seem to work. EDIT: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your feedback! I noticed I also had to remove the Ctrlr.settings in the preferences so that the new version could start without crashing I still don't know why. Once done everything was fine and dandy :) If you leave your sliders individual lookandfeel to "default" they will follow the general lookandfeel. If you want to mix different lookandfeel for exemple main in "dark" and a slider in "grey", you have to specify it in the slider properties. If you close Ctrlr without closing the panel and open it afterward, Ctrlr will get the popups, text fields in the props pane, and alert boxes in Light scheme, but with sliders LnF as previously defined. But if you close the panel, and re open a panel, Ctrlr should get the right command to get updated to the appropriate LoookAndFeel you selected. i'll check the colourpicker thing, I never seen it in the background like your picture, I'll try to force it "always on top" to prevent that. 100% agree with the property pane position, this makes no sense, it's Roman's semantic I'll just change it to "Property pane position" with a tick box "Left/Right". it will be much better this way. Let me know everything you find strange or counter intuitive and I'll try to adjust for the next version. If it's small things here and there, I'll post 5.6.30 with revisions next week. I'm still wondering why the folder to the app preference is "Ctrl" although the bundle is CtrlrX. I changed all that to be sure there won't be any conflicts but it may come from the Windows "Native" file that still have Ctrlr folders location in it. PS: I'll try to Build it on my PC to go for a deep testing and let you know. |
Beta Was this translation helpful? Give feedback.
-
|
@dobo365 FYI: I ported your
|
Beta Was this translation helpful? Give feedback.
-
Some of the "property" were giving an error (red underlined) and were throwing errors on building the sharedCode and compiling the standAlone. After I removed the error (removed some backslashes/ spaces, the errors do not show anymore in Visual Studio, nor building the SharedCode, nor compiling the StandAlone. But my guess is the crash has something to do with a value not being passed on from the combobox. While debugging I can see the combobox come into play and then it crashes with an "unable to read memory" Something with a callback message. Not very helpful, I know. On restarting the application it trips over Coloursettings from the LookAndFeel implementation, probably because it tries to revert back to V3. |
Beta Was this translation helpful? Give feedback.
-
|
I see where it could come from. I will try something. |
Beta Was this translation helpful? Give feedback.
-
|
The first post with the Crtlr crash report was a standalone release build. The last post was all in debug mode. |
Beta Was this translation helpful? Give feedback.
-
|
Forget about the debug mode I never got any version working with it. It finds errors that are not error, for exemple if you change a combo with the callback message Off it will warn something is wrong even if JUCE is allowing it. I'll link combo boxes in the properties to empty void functions for callback messages. It's easy.. We will see if it stops giving the errors. But the combo is definitely doing something :) |
Beta Was this translation helpful? Give feedback.
-
|
This is on my macbook changing the global colour scheme :
|
Beta Was this translation helpful? Give feedback.
-
|
Hi,
Panel attached here : ScalableUI Test_1_0_2024-02-07_23-18.panel.zip These are the settings I used: |
Beta Was this translation helpful? Give feedback.
-
|
I got a reply on email, but can't see it here.
I can't drag that corner. That's the extents of the background before I drag the border. |
Beta Was this translation helpful? Give feedback.
-
|
What's the host ? I don't think it's coming from JUCE because the top level container for Ctrlr is CtrlrEditor which is updated on resize. It means that the host has 2 containers the one you can resize and another one inside. I'll check later this week on my PC with Cubase and studio one but I don't remember even experiencing that issue with 5.6.23. |
Beta Was this translation helpful? Give feedback.
-
|
I just tried it on my Win10 PC and it's working as intended on Cubase 11 and Studio One. It may come from your host.
|
Beta Was this translation helpful? Give feedback.
-
|
I'm using VSTHost, because it's lightweight but I'll try in Ableton Live when I get back to the studio. |
Beta Was this translation helpful? Give feedback.
-
|
It does seem to behave better in Ableton Live. |
Beta Was this translation helpful? Give feedback.
-
CtrlrX v5.6.29 Initial Build
|
Beta Was this translation helpful? Give feedback.
-
FYI on build failures on
|
Beta Was this translation helpful? Give feedback.
-
|
@unityconstruct thanks for the info, I commented those properties because they are useless from now on since JUCE doesn't give access to styling the menuBar so I'll end up removing those menuBar custom colour properties in the next version anyway. |
Beta Was this translation helpful? Give feedback.
-
|
I think it came from a copy/paste I did on an openOffice document I use to take notes of my process. 100% sure it messed up with the characters. |
Beta Was this translation helpful? Give feedback.
-
|
@unityconstruct There you go for the LINUX fix : Let me know if it worked on your side. If you have it working I will cherry pick those updates to my repository. EDIT: Maybe this has already been pushed to Ctrlr Master according to the last comment... |
Beta Was this translation helpful? Give feedback.
-
lol.... I should have already known that answer as I'm constantly porting stuff from PDF to markup or Confluence and you NEVER know what the PDF is going to give you. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
hey brother,
So...
#if defined(__arm__) || defined(__TARGET_ARCH_ARM) || defined(_M_ARM) || defined(_M_ARM64) || defined(__aarch64__) || defined(__ARM64__)
#if defined(_M_ARM64) || defined(__aarch64__) || defined(__ARM64__)
#error JUCE_ARCH aarch64
#elif (defined(__TARGET_ARCH_ARM) && __TARGET_ARCH_ARM == 8) || defined(__ARMv8__) || defined(__ARMv8_A__)
#error JUCE_ARCH armv8l
#elif (defined(__TARGET_ARCH_ARM) && __TARGET_ARCH_ARM == 7) || defined(__ARM_ARCH_7__) || defined(__ARM_ARCH_7A__) || defined(__ARM_ARCH_7R__) || defined(__ARM_ARCH_7M__) || defined(__ARM_ARCH_7S__) || defined(_ARM_ARCH_7) || defined(__CORE_CORTEXA__)
#error JUCE_ARCH armv7l
#elif (defined(__TARGET_ARCH_ARM) && __TARGET_ARCH_ARM == 6) || defined(__ARM_ARCH_6__) || defined(__ARM_ARCH_6J__) || defined(__ARM_ARCH_6T2__) || defined(__ARM_ARCH_6Z__) || defined(__ARM_ARCH_6K__) || defined(__ARM_ARCH_6ZK__) || defined(__ARM_ARCH_6M__)
#error JUCE_ARCH armv6l
#elif (defined(__TARGET_ARCH_ARM) && __TARGET_ARCH_ARM == 5) || defined(__ARM_ARCH_5TEJ__)
#error JUCE_ARCH armv5l
#else
#error JUCE_ARCH arm
#endif
#elif defined(__i386) || defined(__i386__) || defined(_M_IX86)
#error JUCE_ARCH i386
#elif defined(__x86_64) || defined(__x86_64__) || defined(__amd64) || defined(_M_X64)
#error JUCE_ARCH x86_64
#elif defined(__ia64) || defined(__ia64__) || defined(_M_IA64)
#error JUCE_ARCH ia64
#elif defined(__mips) || defined(__mips__) || defined(_M_MRX000)
#if defined(_MIPS_ARCH_MIPS64) || defined(__mips64)
#error JUCE_ARCH mips64
#else
#error JUCE_ARCH mips
#endif
#elif defined(__ppc__) || defined(__ppc) || defined(__powerpc__) || defined(_ARCH_COM) || defined(_ARCH_PWR) || defined(_ARCH_PPC) || defined(_M_MPPC) || defined(_M_PPC)
#if defined(__ppc64__) || defined(__powerpc64__) || defined(__64BIT__)
#error JUCE_ARCH ppc64
#else
#error JUCE_ARCH ppc
#endif
#elif defined(__riscv)
#if __riscv_xlen == 64
#error JUCE_ARCH riscv64
#else
#error JUCE_ARCH riscv
#endif
#else
#error JUCE_ARCH unknown
#endif
|
Beta Was this translation helpful? Give feedback.
-
I try to keep low key for opsec, but if we ever end up on private comms, will definitely pass on brother!
|
Beta Was this translation helpful? Give feedback.
-
**PreAmble: NICE NICE NICE! **
Information Density
in any case.. MAJOR improvement on the LookNFeel! |
Beta Was this translation helpful? Give feedback.
-
Note to self
|
Beta Was this translation helpful? Give feedback.
-
Note to self: Crash: ModulatorList: Tree: Click on grpVoice2 Node [Panel Mode: Play>Edit] |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @unityconstruct ! If ever you want to shrink the property lanes to your tastes it's defined by "preferred height" here on those following lines : I replaced 28px by 36px because I thought it was too cluttered. |
Beta Was this translation helpful? Give feedback.
-
Note to self: Panel Modulator List: componentVisibility: change 0-->1: Save seems to read, not write (value reverts to 0)(view may be read only)
Solution: edit the xml, not the form fields
|
Beta Was this translation helpful? Give feedback.
-
Note to self: CtrlrLabel.h: Inconsistent line endings
|
Beta Was this translation helpful? Give feedback.
-
|
Which version of Juce (Projucer) are you using. I'm using 6.0.4 and not having any luck compiling on Windows VS2019. I'm getting a lot of these errors Severity Code Description Project File Line Suppression State I'll see what the latest Juce 6 version is available. |
Beta Was this translation helpful? Give feedback.
-
saying prayers for ya! no build sux... a black hole of time one never gets back |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I'm getting thousands of errors with Juce 6.1.6 just trying to compile the shared code. I'll try to revert back to 6.0.8. Which version of Visual Studio 2019 are you using. Mine is Version 16.11.8 Most of my errors are in ctrlPanel.cpp
|
Beta Was this translation helpful? Give feedback.
-
|
OK, I succeeded in building the shared code. I recloned the project and ran from Projucer 6.0.8. Fixed the 3 lines in CtrlrPanel.cpp and it compiled. |
Beta Was this translation helpful? Give feedback.
-
|
@Godlike-Productions
|
Beta Was this translation helpful? Give feedback.
-
|
@Godlike-Productions btw: I'm on |
Beta Was this translation helpful? Give feedback.
-
omg-omg-omg-omg-omg-omg-omg-omg-omg-omg-omg-omg-omg@damiensellier
speaking of improved workflows.... been mulling over how implement a XLS -> CSV -> Panel Object parser/builder.
|
Beta Was this translation helpful? Give feedback.
-
|
I did use it recently, but didn't realise it was a new feature! Since which version? |
Beta Was this translation helpful? Give feedback.
-
|
hmmm.. maybe the
|
Beta Was this translation helpful? Give feedback.
-
|
Pardon me but haven't "Multi Select Components" been around for quite a while? |
Beta Was this translation helpful? Give feedback.
-
|
Probably has... I've been on |
Beta Was this translation helpful? Give feedback.
-
|
One other change I've noticed is that Minor Version now has a maximum of 48. Can this maximum please be removed when the next update is done. It's a minor thing, but it's kinda wreaking havok with our versioning on a particular plugin. Preferably a third version box for build number. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, 2048 would be better. We're up to build 190 or so at the moment. |
Beta Was this translation helpful? Give feedback.
-
|
Sure, I'll change it this weekend. Please update the max value ine the xml Line 146 and clear your visual studio project caches to get it updated in your build. Edit : The CtrlrIDs.xml file is updated on CtrlrX. |
Beta Was this translation helpful? Give feedback.
-
|
I have been thinking about versioning and I would propose the following (I think I wrote that somewhere else...) |
Beta Was this translation helpful? Give feedback.
-
|
@dobo365 Yeah I thought about that too. Since we are using JUCE 6, I'll probably go for CtrlrX v6.0.0 when the current version will be approved on the long run without too much issues and we will be able to export VST3 instances with the right IDs. |
Beta Was this translation helpful? Give feedback.
-
|
Since we don't have access to menuBar styling like we used to in 5.3.xxx versions with JUCE 4, I'm thinking about adding "LookAndFeel_V4 Custom" in the global LnF combo that will assign custom default colours via LookAndFeel_V4::colourScheme setUIColour() . We will have windowBackground, widgetBackground, menuBackground, outline, defaultText, defaultFill, highlightedText, highlightedFill, menuText and numColours additional colour properties that will provide custom UI colours for our panels. Those colours are supposed to change the different GUI elements default colours accordingly which is neat. I'll test it and see if it's worth it for v5.6.30. |
Beta Was this translation helpful? Give feedback.
-
Hi everyone,
I just released a new version for the CtrlrX Fork. https://github.com/damiensellier/CtrlrX
It took me almost a month of my free time, I hope you'll like it. I did everything I could to improve the overall design of Ctrlr GUI.
IMHO it's way better and enjoyable to design quick panel mockups without using custom image elements.
From now on, when you launch CtrlrX it starts with LookAndFeel_V4 Light ColourScheme.
If you don't like it, just scroll down the global property pane to the bottom and switch to another look. You'll find different templates from the generic JUCE schemes : Grey, Midnight, Light, Dark. I also left the V3, V2 and V1 style if you feel nostalgic.
I made everything retro compatible for older panels made with 5.6.198 and older, CtrlrX 5.6.29 will automatically switch to the old blue V3 design we all know. The property "legacyMode" will be ticked up.
Every component will get constructed following the current general scheme by default.
You have access to every component (slider, buttons, comboboxes...) individual LookAndFeel Style if ever you want to customize them.
The Juce Colour Picker is now available for any colour property. The times we had to look online for hex values are now over :-)
I invite you to download the source code on my page, and let me know if you find any issue. If everything is fine for Mac and PC, standalone, VST and AU, I will create a release page with all the builds so that anyone can download them.
https://github.com/damiensellier/CtrlrX
Enjoy!
Damien
Version 5.6.29
macOS Intel
CtrlrX-5.6.29-macOS-Intel.zip
CtrlrX-5.6.29-VST3-macOS-Intel.zip
CtrlrX-5.6.29-AU-macOS-Intel.zip
macOS Apple Silicon
CtrlrX 5.6 29 Silicon Mac.app.zip
CtrlrX 5.6.29 Silicon Mac.component.zip
CtrlrX 5.6.29 Silicon Mac.vst3.zip
Windows 10
CtrlrX-x64-5.6.29.zip
CtrlrX-x64.vst3-5.6.29.zip
Beta Was this translation helpful? Give feedback.
All reactions