I want to write my own utility so I can drop the dependence on pborca and then I will probably release something. To work around this I take the errors and then parse the raw source to find the actually line number within the source and then return my own errors which are then easy to pick up with a problemMatcher regex in VSCode. The problem is the line numbers that are returned are relative to the script itself and not the raw source of the whole object. I wrote another program in NodeJS that dynamically generates a script and then calls this program to compile the object I am currently editing. So I found this project called pborca which is similar to the official orca script but will allow you to compile a single source file into a PBL which isn't something that you can do in the official orcascript: If you edit a source file outside the IDE it doesn't automatically see the changes and update the PBL. ![]() The problem is it doesn't work the other way around. For example:Īnytime you edit something in the PB IDE these raw source files are instantly updated. Well first of all when you enable source control in PB2017/19 it exports all the source to a folder named ws_objects.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |