The advanced rename in script mode seems to always uppercase some characters here and there.
If the language is vbscript then that would be quite ok, however other languages might be case sensitive
and requires the words not to be uppercased where they shouldn't.
The editor seems to be ok most of the time as long as it is vbscript or javascript, but it sometimes happens
with javascript too (I've encountered the editor trying to uppercase "F" in "function").
With other case-sensitive languages, it doesn't really go so well.
Why not have it stop "prettifying" languages it doesn't know?
In other words, if it encounters "@script perlscript" (or anything else that isn't vbscript or jscript) at the beginning, then have it stop any "prettifying" right there.
It might as well stop any highlighting at that point too, because it is likely that too will be wrong as it doesn't know the language.
Try typing (or copy and paste) this in the rename script editor with v11.1:
@script perlscript
sub OnGetNewName{
The "s" in "Sub" is suddenly uppercased, and you'll have to trick the editor (by typing Ssub, then use backspace on the "S"), until the editor modifies it again.
That "S" is rather significant in a case-sensitive language, so it causes the script to fail.
To be more exact.. It changes the case assuming everything is vbscript (which isn't case sensitive), no matter what it is.
It does the same even it you just paste into the editor.
Then I found the "Change case" menuitem, and thought hah, maybe it's possible to disable this code "fixing",....it wasn't.
That option changes the case of everything that it doesn't find worthy of prettifying.
11.1 beta 1 still prettifies code that is PASTED into it (such as the example above), so the @script check probably isn't done in that case.
When it does, it also enables prettifying everything I type afterwards..until I make any change to the first line (iow, add and delete a char).
It seems to work properly if I just type code manually..so far anyway.
This seems to work properly so far in 11.1.2 beta.
Now if only the DO's editor(s) supported Shift-Ins (Paste), Ctrl-Ins (Copy), Shift-Del (Cut), Alt-Backspace (Undo) it would be even better.
I'm terrible at the "new" keys for them. Just about everything supports those keys as alternates, so I guess there's more
than me which can't really get used to the "new" ones.
We'll add them in the future. I don't think Ctrl-C/X/V/Z qualify as "new" though, since they were standard at least by Windows 95, which came out 19 years ago
Nice
lol, well I guess I'm an old-timer in that regard.
I guess it's because they're so easy to use compared to having to look for keys in the middle of the most crowded part of the keyboard.
I know, excuses and such..But, well.
If it is standard layout then it is the upper left of the six keys above the arrows.
But the strange thing is that I barely remember (or care) where anything is when I see it, but my hands know.
Just for comparison, here's mine:
Its a gaming keyboard, but it is perfect for coding.
ROFL.
Btw, your keyboard seems perfect to train writing without looking down.
But when you see my keyboard I'm sure you can relate to the "most crowded part of the keyboard"
I'm using 11.5.5 Beta and this is crippling JScript editing. Is there any way to turn off the "prettifying"? There are lines that can't be fixed using the backspace key trick. If there are 2 key words on the same line it "corrects" the other when you "backspace fix" the first. So if you want to fix "If" and you type "Iif" followed by backspace, it reparses the whole line and switches the latter keyword (eg True) to Titlecase.
Spiro
I always close the button editor right after changing or inserting the @language modifier. In some previous versions, not doing so could lead to crashes, especially in combination with changing the type of the button. I excuse for not filing a record and investigating how to reproduce this, but I was short on time in these situations.
The jscript-highlighting should work as expected after reopening the button editor, it does so for me at least.
Thanks for reply. Not working for me unfortunately. Sanity checking... I'm putting: @language JScript
as the first line, closing the button editor, then reopening it. Is that right? Still getting frustrated by the auto Title case.
Workaround for the moment is to edit the .dop file using Notepad++. Its slow though because I have to launch a new lister every time to test the changes.
thanks,
SPiro
Change @language to @script and it should be fine. @language was used during the Opus 11 Beta but dropped before release and although it still works to set the script language the editor doesn't detect it, and so the syntax highlighting will be wrong.
