Forum Replies Created
i’ll have a look if i can build ctrlr at those versions
I uploaded 6.0.25 can you tell me if that fixes the issue, and if that can be used for your purposes ?
i’ll have a look asap and see if i missed something here
i’m sorry about all that, there is a bug in there somewhere and i need to fix it, i’ll try to at least make a workaround so that all the work doesn’t get lost. i promise some bug fixes soon
Should be better now
Yeah there are loads of UX issues i need to address and I will. I have some priority work in the engine though so this must wait, i need to stabilize the code and cleanup/order the luabind/lua stuff, there is a new branch on github that deals with that, once that’s done i’ll get to the UX part.January 21, 2017 at 10:50 pm in reply to: [solved] Problem compiling on ArchLinux ARM (Raspberry Pi 2) #70939
I want to migrate the Linux build to Cmake, i already moved the windows subsystem away from Projucer so it’s now pure VisualStudio projects that I will update. I want to do the same with Linux but for cmake, and the same for OSX for Xcode. Projucer is a pain in the ass and i will only use it for compiling resources, and in the future i will drop that too and just do that myself (by either distributing the file and opening them in the program or compiling them to .h/.cpp files with my own small program that will be built during the build process on each platform).
If you’d like to help with going to Cmake on Linux please submit patches on github i’ll review them and merge them asap.
I’ll try to have some static mockups and i will present them here, hoping for feedback.
Oh yeah one of the programs i told the UX person to look at was Max so i think the idea might go along this route.
Well i’m trying to make it more like a “photoshop”/”max” program, so that in edit mode those toolbars “float”.
The big problem is the property sidebar, there are loads of those properties and some of them have very long descriptions, i don’t have that figured out yet.
I hope to clean the colours fonts and sizes of all objects to make it look more “natural”.
Once i’m done with all the project/build-system changes i’m doing i’ll get to that, i’m not planning on adding any new features for now. It’s all code stability and User-eXpierience for now.
I know that the UI of Ctrlr is a mess and i wish i could make it better, but i just can’t i don’t know how, i hope to get a UX specialist to help me sort things out and guide me. I’m actually in talks with someone who does this.
As for python, i will never implement python in any shape or form, i think this hole idea of Python as a programming language is a bad one, i don’t like it, and i won’t change my mind.
i fxed that, it should be in sync now, i’ll try to make those commit messages a bit more descriptive
ill try to sync this up, i really didn’t do anything on this website for a long time, it’s time to fix things up, thank you for the reminder
You should read the commit log on github: https://github.com/RomanKubiak/ctrlr/commits/masterJanuary 2, 2017 at 3:04 pm in reply to: [solved] Problem compiling on ArchLinux ARM (Raspberry Pi 2) #70856
So whats the main problem now ? I can try to do arm builds on ubuntu as i have a spare odroid xu4 octa-core not beeing used, i can set up a build machine on it.
I’m aiming at doing cross-compile builds for ARM so i can build them on x86.January 2, 2017 at 2:00 pm in reply to: [solved] Problem compiling on ArchLinux ARM (Raspberry Pi 2) #70854
The build system is currently beeing worked at (have a look at the github commit messages)
I’m working on making the build faster and more efficient. I found a way to include boost only in SOME files not in all and i’ll make my own Makefiles and project files (i’m dropping Projucer for project management)
Make Visible on Canvas, moves the selected object to position 0,0 on the canvas so you can see it if you dragged it outside the canvas or resized it to something invisible.
Can you take me through the process, what are you selecting, a group of objects – does it mean a group component with some other components inside it, or just a bunch of components selected. What do you mean copy to another project do you copy/paste between two open panels in Ctrlr ?
You should use BigInteger the native JUCE class, it’s bound to Lua, the CtrlrLuaBigInteger is an obsolete class that is there for compatibility puproses. The bit.* functions will remain it’s a low level implementation that is there for performance purposes
all bit functions will be back in next builds, i will fall back to lua 5.1 since 5.3 is giving way to many issues to fix.
I will add the JUCE OSC stuff but alongside this implementation and you’ll be able to choose what API you want to use, i don’t want to break anything, often people use it just don’t say anything about it here.