I was wondering why the long time between betas – now we know! [:D] So on to the initial evaluation:
Any chance of adjusting the text line height based on font size? I’m using the Lucida Console font. Sizes 6 through 11 all have the same line height. I currently use size 9 and occasionally smaller when I need to see more lines on the screen, but that no longer works. It sounds picky, but when dealing with large package bodies (>1300 lines), it makes a noticeable difference.
I’m not sure if the reduced vertical density from the text line height is playing optical tricks on my old eyes, but do the fonts look thinner?
Can the datatypes be pulled out of the keyword styling list by default? The keyword highlighting is taking precedence over datatypes, making the datatype highlighting void. The workaround is obvious, of course. [:)]
Any possibility for BEGIN/END block highlighting?
undo doesn’t seem to work after hitting . Eep!
I’m excited to play with the new editor more! And now that the first year+ long project is done, I just may have time. I apologize in advance… [;)]
Not sure. I see this too. I'm not sure if it would help any, but Scintilla supports text zooming. Hold CTRL and use the mouse wheel. It makes it smaller, but appears to paint a little differently than 100% zoom and using a smaller font.
I set mine to Lucida Console 10 and compared 12.6 to beta and both are using the same dimensions to paint and when blown up in Paint all of the pixels appear to match verbatim. Scintilla supports a few different drawing technologies. I could slip a hidden
INI option in for you to play with and see if it's worth surfacing as a real option. I've been hesitant to option everything I could have to avoid unnecessary clutter.
This is a bug. It was working properly before and I broke it. Datatypes need to be in keywords because datatype highlighting is dependent on an active connection. Toad populates the highlighter with datatypes that are valid for that version of Oracle. As
I write this it seems like overkill. A master list that contains all valid datatypes is probably sufficient. At any rate, I'll fix the glitch for next beta.
A little later in the cycle. This is one of the most challenging areas and I haven't had any time to fully wrap my head around it. Scintilla is great because it provides all of the building blocks necessary to do almost anything; however, it does very little
automatically. There are two ways to approach this. The first is to add code similar to the old component which will take time and add overhead. The second is to use the parser which will provide more accurate results, but the dynamic highlighting will be
delayed in display until we have results back from the parser. We're already digesting the parser results so this method adds less overhead and will be more accurate.
!! Actually it looks like it's working for me, but not working properly. If you have auto indent option enabled the first CTRL+Z removes the indent and a second the newline. Is this what you're seeing? I'll fix this.
I was wondering why the long time between betas -- now we know! So on to the initial evaluation:
Any chance of adjusting the text line height based on font size? I'm using the Lucida Console font. Sizes 6 through 11 all have the same line height. I currently use size 9 and occasionally smaller when I need to see more lines on the screen, but that
no longer works. It sounds picky, but when dealing with large package bodies (>1300 lines), it makes a noticeable difference.
I'm not sure if the reduced vertical density from the text line height is playing optical tricks on my old eyes, but do the fonts look thinner?
Can the datatypes be pulled out of the keyword styling list by default? The keyword highlighting is taking precedence over datatypes, making the datatype highlighting void. The workaround is obvious, of course.
Any possibility for BEGIN/END block highlighting?
undo doesn't seem to work after hitting . Eep!
I'm excited to play with the new editor more! And now that the first year+ long project is done, I just may have time. I apologize in advance...
Playing with the zoom now – ooooooooooh! This looks promising!
Yeah, I was going to screenshot both then compare, and I got to way overthinking (overcriticalthinking?) it. Does the screenshot compress the output? Could the compression of two different shots end up with the same output? Could the image rendering of the zoom of the screenshots affect the quality? Etc. Like my overuse of smilies, I’m thinking this one should probably just be skipped…
Coolness!
No worries! (from me at least)
I don’t have indenting on. I initially thought the lack of undo (and no Oracle DBA likes that) was due to the syntax highlighter popup, but in the same line it’s all good. When hitting return, I do see a flicker that might be the syntax popup, but I can’t be sure.
Thanks much!
Can you send me your user files offline? michael.staszewskiquest.com
Thanks,
Michael
On 12/11/2014 12:40 PM, Rich J. wrote:
RE: Scintillator feedback and questions for 12.7.0.26
Reply by Rich J.
Hey Michael!
Playing with the zoom now -- ooooooooooh! This looks promising!
Yeah, I was going to screenshot both then compare, and I got to way overthinking (overcriticalthinking?) it. Does the screenshot compress the output? Could the compression of two different shots end up with the same output? Could the image rendering of the zoom of the screenshots affect the quality? Etc. Like my overuse of smilies, I'm thinking this one should probably just be skipped...
Coolness!
No worries! (from me at least)
I don't have indenting on. I initially thought the lack of undo (and no Oracle DBA likes that) was due to the syntax highlighter popup, but in the same line it's all good. When hitting return, I do see a flicker that might be the syntax popup, but I can't be sure.
Thanks much!
Rich
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or Unsubscribe from Toad for Oracle - Beta notifications altogether.
Toad for Oracle - Beta Discussion Forum
#1, this was an oops and it's fixed for next beta with clean user files only. To fix in the current beta modify the font for the "Brace Highlighting" style from 11 to Default.
I was wondering why the long time between betas -- now we know! So on to the initial evaluation:
Any chance of adjusting the text line height based on font size? I'm using the Lucida Console font. Sizes 6 through 11 all have the same line height. I currently use size 9 and occasionally smaller when I need to see more lines on the screen, but that
no longer works. It sounds picky, but when dealing with large package bodies (>1300 lines), it makes a noticeable difference.
I'm not sure if the reduced vertical density from the text line height is playing optical tricks on my old eyes, but do the fonts look thinner?
Can the datatypes be pulled out of the keyword styling list by default? The keyword highlighting is taking precedence over datatypes, making the datatype highlighting void. The workaround is obvious, of course.
Any possibility for BEGIN/END block highlighting?
undo doesn't seem to work after hitting . Eep!
I'm excited to play with the new editor more! And now that the first year+ long project is done, I just may have time. I apologize in advance...
Rich, next beta will start to trickle in support for #4. It's currently limited to BEGIN-END and CASE statements, but it will be expanded. It's also been changed to use the parser which provides very accurate results and the ability to expand it to highlight all important tokens of the current block as asked for in this popular idea. The "Current Block" style used for the highlight can be changed on the Editor|Font and Styling options page.
Once I have this complete the same logic can be used to reintroduce the folding ranges that were present in prior releases.
Reply by Michael Staszewski
Rich, next beta will start to trickle in support for #4. It's currently limited to BEGIN-END and CASE statements, but it will be expanded. It's also been changed to use the parser which provides very accurate results and the ability to expand it to highlight
all important tokens of the current block as asked for in this
popular idea. The "Current Block" style used for the highlight can be changed on the Editor|Font and Styling options page.
Once I have this complete the same logic can be used to reintroduce the folding ranges that were present in prior releases.
