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.

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.

autocompletion for all packages is really necessary

Please have editor 'clean up' mixed tabs and spaces, rather than flagging an indentation error, or at least have it flag as mixed tabs and spaces, instead of a generic indentation error.

Sizing the Script editor window better.

Every time I reopen it I need to either scroll or expand the window.

I assume it's opening at about the typical terminal sizing, but In the world of 4k, 80 columns of text is painfully small.

If it could ome up with double or triple width, or detect length of text columns to adjust accordingly.

Further, there seems to be a maximum width on the scroll, where you need to actually use the arrow keys or end key to get to the end of your script because it only scrolls for so long. When you could have something along the lines of:

system.gui.getarentWindow(event).getComponentFrPath('Root Container.Text Field').text =

system.gui.getParentWindow(event).getComponentForPath('Root Container.Group 1.Group 2.Dropdown'.data.getValueAt(0, "Value")

You really need more columns, a wider screen by default, or something along those lines.

In 7.8.x the script playground has some of this improvements... on the left side, has marks for find/todo (plus code folding and themes) and on the right side has autocompletion for all packages (including project and shared, besides system).

There are plans to unify all the features for the script editors for shared and projects resources?

There is however a big problem with the CTRL+ ForwardSlash Method. If you program on a keyboard with a layout other than the US-Layout you can't use that.

For example on my german keyboard I have to press SHIFT+ 7 to get a Forward Slash. So it doesn't work for me.

Integrating the code/text editor features of Atom/SublimeText would make things much more efficient.

CTRL-Mousewheel for font size was done in 7.7.5 / 7.8.0

When we reference a tag or a property in script, it will be convenient to be able to select multiple tag or properties to add all the references in one shot.

It could be long open and select tag or properties one by one.

I would also like to have the ability to change the font color and background color of text types such as comments and string text. I'm in my 60's and my eyes aren't any younger. I find it hard to read these light gray comments at times. In Visual Studio I change them to black text on a yellow background so they stand out more.

And also, red line when a function/method/class isn't created yet. Just like in netbeans/eclipse for easier debugging.

Another improvement that would make it great would be to show a TreeView of the available scripts at the side of the Script Editor when it is floated from the main designer window. It's a real pain when the script editor is in a separate window and I have to scroll in the Project Browser to open a new script and then back to find the window I was working on.

CTRL + ForwardSlash has no effect on windows ???

A cool swing editor is available at http://fifesoft.com/blog/

http://fifesoft.com/projects.php

http://sourceforge.net/projects/rsyntaxtextarea/