Two words. Dark Theme. Thats pretty much it from me right now.
- The ability for ROBOTC to open a CORTEX program. Basically the ROBOTC should have a translator integrated into the software (NOT integrated in the CORTEX) then translate the CORTEX code into a ROBOTC form that is uncommented(Like in case if files were deleted, forgot to bring the USB to a competition, etc…). It shouldn’t be that hard because the program should be able to translate from ROBOTC into the CORTEX version, just reverse it!
- A TON more bug and crash fixes.
- Dark Theme option (Maybe same to VEX Forum too
)
So you want to go back from compiled code and reverse it to regular code? That’s pretty complex. Like, that’s not easy at all.
Ya the big thing specifically is that it isn’t a 1:1 transformation.
If I’m understanding correctly, that can be accomplished in RobotC as it stands currently.
Basically I’m not saying for a 1:1 transformation. I understand it truly isn’t a 1:1 transformation, and what I’m suggesting is that they could have it be transformed back anyways with the code that the robot has in case of any emergencies. Like, I am sure the commenting wouldn’t be there nor the motors and sensors setup. But if this makes any sense, I am wondering if it would be possible to be able to get the program back into ROBOTC with what’s given from the CORTEX, even though it isn’t that much info, but just for emergencies.
Oops, yeah after searching on the forum I realized that… Okay yeah I’ll delete it from the last post.
Well, it seems like the first one is too complicated to do, then the last one was too simple that it was already practically in ROBOTC. But they were just suggestions though
– Function pointers
I’ll bite. After doing C programs for decades (Unix 5th Edition) I’ve used function pointers twice. I understand the possible use case, but I have to ask “Is that really high on the list of things to get done”. (Or the possible, “well the todo list got so low, this is now on top of the list”. )
I can see a “Dark Theme”, even though I’d never use it since I love black text on a white background (stemming from even more decades of reading things called “books”.
I hadn’t realized that there were that many bugs in RobotC, it’s been awhile since I’ve run across ones that were not easy to work around.
Wheat on dark navy is my preferred color set. Not quite the high contrast on the deep black background and I like the wheat color over the gray scales typically used. All personal preference here. I like the less eye strain of the dark color scheme.
Wheat: Hex: F3E7A9 RGB: 243-231-169
Midnight Blue: Hex: 191970 RGB: 25-25-112
(Option 2) very dark Blue: Hex: 001934 RGB: 0-25-52
ROBOTC already has a method of recovering old code. Open the Recycle bin on the machine it was worked on and you will find old versions of your code. Then of course there are the professional ways to solve this problem. (version Control, back ups etc)
This isn’t always possible. For example, at my school, the computers are ‘frozen;’ basically, they get re-imaged with a clean image from the beginning of the year on every restart. So nothing from the Recycle Bin is saved.
I do, however, advocate using a cloud-based VCS (such as Git with GitHub) for this purpose.
You have a point there! 
Lol but my bin gets literally spammed with ROBOTC Program files moved to the recycling bin, plus I said “Like in case if files were deleted, forgot to bring the USB to a competition, etc…” so like bringing a USB to open it to another computer but you forgot to bring the USB.
Sure, an additional dark theme would be nice, but that isn’t going to make everybody happy, is it? I’d rather have a plugin system to modify or add to the existing ui and functionality. Something generic enough to be powerful, but abstract enough to be easy to use after learning the system.
plz don’t let this be a dream
Function pointers and atoms/eclipse/some other ide integration. I think rerun would make programming too easy and encourage hard coding, instead of sensor usage and discourage learning how to program.
This might just be a feature that I’m not using right but the robotc emulated robot is awesome and it would be even cooler if you could plug your remote into the computer and use that controller to manipulate the currently emulated code…
Full ansi C support(better for cpp support) (I hope this can be solved with a stable ready-made ansi C frontend and generate opcodes using the AST generated by that. like Clang and LLVM)
Compiler that supports multiple files(Linker)
Better editor or Eclipse plugins(Using jssc or something else)
Enable users to insert pure C or ASM without VM (GCC toolchain maybe)
Advanced file IO (though rcfs is pretty good, but I just can’t delete files)
Better opcode format (java bytecode maybe a good reference)
Object Oriented Programming
Plugin support (some APIs can be released)
Open Source
VM optimization
The debugger thread should be separated from the GUI thread the main thread(there’s such a long delay while using the wireless programming kit)
I know that some features may make the VM unstable, but I found it neccesary for advanced programmers)
Well actually some platforms such as ConVEX and PROS seem to meet my demand, but a RTOS is unstable indeed, as the leader in VEX edr software development, i hope that there will be a safe way to do these all above.
How about compatibility with Linux & OSX? I’d love to be able to run RobotC on a Raspberry Pi or my teammate’s Mac.
What about the ability to control the robot by the PC if the robot is directly connected to the PC as if the keyboard were to be a joystick? Like the WASD keys will be to represent the left joystick and the arrow keys would be for the right. And this can be toggled by a certain thing in the toolbar.
That would be nice… but rather than just toggling rather parts of the keyboard are on or off i think it would be better to make it so that you can make certain keys represent certain parts of the joystick.
I.e. instead of saying that P = Btn8u and you can just toggle it; you let the user say what the P key equals.
I REALLY like that idea though… that would be super useful.
i wish it was just purchasable instead of having to buy vex crap to get it(i think thats how you
quote)