|
Post by mueh on Nov 22, 2021 2:30:37 GMT -5
George: Thanks it is now much better after 21325 . For Full screen the problem is now gone (seems that last (right) Pixel's are not shown for last character) untill you switch to window and back to full screen . For Window only first pixel's of next character are shown ( Previously the left 2 pixel's ) Could you decrease the pad amount once more to avoid 1'st (left) pixel's of next character to be shown ? Here screen shots with screen magnifier and how the next character looks ( 'M' character yellow sometimes inverted) Just FYI propagating to shorter lines occures with 21325 for terminal font ( not for Courier new)
|
|
|
Post by George on Nov 22, 2021 9:56:03 GMT -5
MUEH: OK, one more try, at this point I'm no longer even sure just what or whether this next version is different from 21325.
If it's still no good, I will not try again until we can come up with some scenario that fails on my system. I just can't keep fiddling without being able to see the effect.
George
|
|
|
Post by mueh on Nov 23, 2021 2:15:35 GMT -5
George : Version 21326 shows now 2 left pixels . 21325 was better because it only showed 1'st left pixels . Sorry that i didn't mention that you have to colorize this characters and change window size . Hope that i have now a repeatable scenario . VIEW dopr f EE all +yellow change window size or switch from full screen to window mode and you should see the additional left two pixel's of next character after scrolling right with col 82 last col on screen . Thanks for your patience . Here the file and screenshot . if you can't reproduce stay with 21325 change . dopr (854 B)
|
|
|
Post by George on Nov 23, 2021 9:44:13 GMT -5
MUEH: OK got it, now I have a pointer to a different area to look at. Having the next characters with different attributes (any differences) takes a different path. Stay tuned.
Thanks for the repeatable demo.
George
|
|
|
Post by George on Nov 23, 2021 12:58:00 GMT -5
MUEH: OK, I think I've got it now.
I wish we'd never put in the 2 pixel left and right margins in the graphic window. But after several attempts at re-writing the logic in there I think it's all in place. For a while I thought I was playing whack-a-mole - get one bug working, and one of the others re-appears, etc. etc. All to avoid that 2 pixel right margin.
New Beta to be posted
George
|
|
|
Post by George on Nov 24, 2021 9:23:14 GMT -5
Robert: No sweat, the idea was fine. Without it the leading/trailing characters butted up against the frame and were hard to read.
You know me, I took the easy route and didn't worry about printing more text than would fit because GRAPHIC PRINT just threw it away without complaint. However GRAPHIC PRINT still 'used' those extra couple of pixels.
Forced me to 'do it right'.
George
|
|
|
Post by mueh on Nov 30, 2021 5:33:08 GMT -5
George: With 21327 the first Characters (underscored) are unreadable (white) in FM Help lines . Thanks P.S. What do you think about idea of FM option to sort it either old style or with StrCmpLogicalW in FMSortUp FMSortDown function ?
|
|
|
Post by George on Nov 30, 2021 11:19:58 GMT -5
MUEH: Sigh! Made another minor correction to DoPrint, now looks a lot better. I never have Help displayed which is why I never spotted it.
The Sort option should be easy, it's just choosing to call StrCmpLogicalW or StrCmpIW to do the compare. 99% of the work is just adding the new option and documenting it. The default will be the current method (the one you don't like)
George
|
|
|
Post by George on Dec 1, 2021 12:59:30 GMT -5
Robert: Well, as it turns out, the StrCmpIW API is not (as it indicated) a simple ANSI, non-logical compare. MUEH discovered that it STILL mucks up the handling of leading - characters. So we've gone to a hybrid of API for logical, and native PB compares to do the simple ANSI.
George
|
|
|
Post by George on Dec 1, 2021 16:26:40 GMT -5
Yeah, MS API's can be a mystery. Even reading MSDN, it not clear just what's what. I know I read the API was supposed to be normal ANSI, but now I can't find that reference on MSDN, maybe I mis-read it.
George
|
|