Make sure your default editor for .lua files is VS Code. The extension relies on Rojo for opening files as it doesn’t have access to any file paths, and Rojo will always use the default editor.
To change your default editor on Windows:
Right click any .lua file
Click “Open with…”
In the dialog that pops up, find and select Visual Studio Code, then check the “Always use this app to open .lua files” box, as seen here.
Press OK and try opening a script again
I don’t own any Apple devices, but the process should be roughly similar on MacOS.
@UnlimitedKeeping
Same as above. Also, make sure the script is not inside of a .rbxm file. Rojo cannot open these files.
I tried a primitive method by simply changing the code editor that the .lua files opens to notepad, and it worked just fine, but when I swapped back to VSC, it still did not work.
so, from that it seems like my VSC can’t open .lua files into the project workspace. yet from the folder explorer in VSC, I can open the .lua files perfectly fine without any problems.
Not sure what would cause that. Best I can suggest is that you reinstall VSC and make sure you’re on Rojo 6.0.0rc1. Also check Rojo’s output for any additional information.
I solved the problem, apparently you cannot use this with the rojo VSC extension, I changed to the binaries, and then this extension worked just fine, seems like the problem lies within the rojo VSC extension.
note to everyone experiencing the same issue, do not use the VSC extension if you’re planning on using this extension, it will not work.
You’re correct; I’ve reproduced the issue on my device. Rojo returns as usual (no error information, all checks pass), but does not open the file in VSC. I’ll contact evaera and see if it can’t be resolved quickly. For now, just use the CLI.
Now that it’s been just over a week since I released this, if anyone has any feature requests or has been experiencing any bugs, feel free to file an issue here. Make sure to label it accordingly.
Not a bug, but it seems that when clicking a module script in the explorer, it takes almost one full second to actually open up the script (or jump to the script tab if it already is open). Is this the case for everyone?
I don’t know if a full second is normal (it usually takes less than half that for me), but I cannot control how fast they open since Rojo handles file opening. Is your system or network under load?
Been using this plugin for the past two days, it’s really great! I have a couple issues that I posted on the GitHub page, namely disabled scripts not being greyed out, and having to manually type in the project name every time I want to connect Rojo UI (even though the Rojo project config file contains a project name field). Are you actively looking at issues on GitHub? Can we contribute to the project?
Yes, I actively check issues, but I’m currently swamped with coursework. I’ll try to get to the features you requested as soon as possible, but feel free to contribute!
There should be an R at the bottom of the activity bar to the left. Click that and the explorer & properties panel will show. You can then click the + at the top of the explorer panel to connect to Rojo.
