74
script editor improvments
in progress
lionel MAZEYRAT
I spend lots of time in script editor...
7.7 editor include very cool new features, but still need a few add !
- color marks for todo like in eclipse
- coor marks for found occurence of a find comment
- right click on function list to copy full function path
- auto comment, uncomment lines of code
- autocompletion for all packages
- ctrl mousewheel to increase text font size
Log In
Activity
Newest
Oldest
P
Paul Mangels
Want to +1 several of the suggestions here. A lot of this seems like basic stuff for a Python editor, and I also would be happy just having an external editor to use.
- Auto-complete/IntelliSense for custom functions. It is super annoying to have to manually copy or type paths. If the function is available from the scope I'm working in. If I can call the function, I should be able to auto-complete it (for example, global scripts in a tag script, etc).
- Basic copy-pasting. I don't know what exactly is happening under the hood, but copying and pasting code results in incorrectly tabbed/formatted code 95% of the time. It's not a big deal for a couple lines of code, but any decently long script it is a serious inconvenience and potential source for errors.
I do also agree that the most complete solution is probably to allow easy integration with an external editor (VS Code is my personal preference) rather than a la carte adding these to the Ignition editor.
B
Ben Newman
Honestly a better approach would be to just have a feature that will allow us to connect an external python editor to the Gateway.
VS Code
PyCharm
Notepad++
Atom
Sublime
Etc.
B
Ben Newman
variable renaming would be really helpful. Find/Replace is not the same.
M
Matt Boog
Exposing the format of all functions, like the system functions are, would be helpful. Being able to add comments to the function format would be icing on the cake. Also being able to quick-view or jump to a function definition would be helpful.
M
Markus Gottschalk
Could you please include a Replace function? There is Find but not Find/Replace
P
Paul Griffith
in progress
c
clint.banzet
I'm sure there's a reason for this and I'm sure it comes up a lot, but why can't we drill down to just a component when using the "Insert Property Reference" button? Why must we "choose a bound property in the tree"? It is extremely common to set a variable to just a component in the code and then use that variable throughout the code instead of the full reference, yet even in the videos I watch, the script author has to drill all the way down to a bound property and then "back off" the property to get to just the component reference.
c
clint.banzet
I am sorely missing the ability to expand and collapse loops and if statements like I have in Notepad++.
Along with that, it would also be nice to see the tab stops like in NPP when editing Python.
But, don't throw the baby out with the bathwater! I like the text coloring better in the current script editor better than the default coloration for Python in NPP.
N
Nader Chinichian
autocompletion for all packages is really necessary
Load More
→