Forum Replies Created
-
AuthorPosts
-
Thanks for the feedback mat, glad you are finding it useful. I definitely want to do more with the output and debugging and will look at that in a future update. Integration with the Atom Linter package is still on my radar as well
I’ve just pushed up v1.1.3 which has some bugfixes and small improvements to the autocompletion:
- Bug fix: improved parsing of one line if statements
- Bug fix: improved private block parsing
- Improved global and constant variable lookup in autocomplete
Ok, I’ve published v1.1.2 which should hopefully resolve some of these issues.
- The package now has a “Save on Build” setting (on by default) which should save all open editors before building
- Print statements should now be broken up line by line
- I’ve tried adjusting the padding / margin on the output panel to help with the unreadable text at the bottom of the window. I wasn’t able to replicate the problem unfortunately though so I’m kind of groping in the dark here. Can you let me know what font & font size are you using, and what OS?
I wasn’t able to make the panel resizable; I had assumed that would be straightforward, but unfortunately atom panels don’t have that functionality by default, and I don’t have the time right now to code it in from scratch. I could put in another package setting so that you could specify the height in pixels of the output window or something though, and/or possibly adjust the docking position (top, right, left, etc.)…would that suffice for you?
Thanks for the feedback, glad you are finding it useful
All of those things should be doable. I will take a look at them for the next update.
Ok, v1.1.1 is now up with basic autocompletion. Here are the notes from the README:
Autocompletion depends the autocomplete-plus package, which should be installed by default in Atom. If not, you can install it via the package manager.
Once you have entered a path to your monkey installation (see Installation above), the package will automatically parse your modules folder, as well as your local project tree for monkey2 files. It will then try to provide autocompletion suggestions based on what it finds.
Currently it will ignore anything within a Private or Extern block. It also cannot parse the type variables assigned in the shorthand format Local var:= Image.Load(…, so to get autocompletion on your variables, define their type explicitly, eg. Local var:Image = Image.Load(…
Hey, that’s good to hear. Regarding autocomplete, yes it would be great to have. I am still working on it. I’ve managed to get a boilerplate Atom autocomplete-plus provider working, but I haven’t populated it yet with proper suggestions. I hit a bit of a wall with that and some of the highlighting and indentation bugs, as my regex skills were not up to the task. I decided to step back a bit and brush up on that and then jump back in. I will post back here again when I make some proper progress.
-
AuthorPosts