Why can’t running code use the same line-counting system that DDE uses? If I log a message “error on line X” and open the code in DDE, I frequently find that line X is a blank line, or has code completely unrelated to the error.
Another problem, perhaps related to code completion: DDE sometimes goes nuts and randomly switches back and forth between normal text entry mode and some sort of psychotic insert mode, where some characters are inserted at the cursor, some before, some after the next letter, some disappear into the void, and sometimes the cursor itself jumps around.
This makes development in 8.5.1 a complete nightmare. I hope we get a patch to this mess ASAP.
Are you looking at the line number in the relevant sub or function? If your highlight is on the agent or script library name, remember you’re getting the line number for the whole code, not the line number for the individual sub or function your error handler is within.
I use OpenLog extensively and haven’t found the error lines to be erroneous, when looking at the relevant sub or function (which may just be Initialize).
Been using 8.5.1 designer for a few months now and find it rather annoying to use!
Cursor just randomly jumps back one character whilst typing in code, happens quite often to!
Auto indenting doesn’t work if you insert a condition to existing code!
Intellisense just is not very good at all!
Opening a design element from the view/list of them is very slow sometimes. It looks as though you’ve not double clicked or pressed enter to open say a form. But then after what seems like forever it opens!
Why can’t running code use the same line-counting system that DDE uses? If I log a message “error on line X” and open the code in DDE, I frequently find that line X is a blank line, or has code completely unrelated to the error.
Can you clarify which type of error message? Is it the one that appear in the Problem view or the one returned from ERL function?
For the one found in the problem view, the line number is related to the entire script (including the hidden comments that are not shown in the editor). This is why the number do not exactly match, however, if you double click on an error in the problem view, the cursor should be in the correct line.
For the ERL function, here too there is a mismatch because as opposed to the old editor, the new editor put classes in their own section instead of in the declaration section. While putting the classes in their own section is a huge improvement, the side effect is that line number returned by ERL are now not accurate. This is why we’ve added a “Go to ERL” menu to position the cursor to the right line.
Another problem, perhaps related to code completion: DDE sometimes goes nuts and randomly switches back and forth between normal text entry mode and some sort of psychotic insert mode, where some characters are inserted at the cursor, some before, some after the next letter, some disappear into the void, and sometimes the cursor itself jumps around.
Are you able to reproduce this issue consistently? If so, can you please post the exact steps to reproduce?
Just start typeing in a large script library (but actually code the makes sense).Exact steps to reproduce are difficult, because if you re-executes, apparently it does not happen again. You sort of have to catch the editor ‘off-guard’. For instance, what i had just now:
I want to declare an extra var in a sub, so on an empty line i start typing ‘Dim varname as Integer’ without looking at the screen, but at the keyboard, as i’m not a good typist.
When i look at the screen i see:
‘im varname as IntegerD’
This is just an example, it happens also with methods or properties of Notes objects or custom classes.