|
|
Post by George on Jun 10, 2015 9:47:43 GMT -5
Re: Fonts. I have seen this type of thing before, as you have Robert. Remember the problems of resizing windows properly and getting all the sizes of things correct? During that, I do remember that the reported font height/width that comes back from Truetype font is not entirely trustworthy. Even fixed width Truetype fonts still seem to be susceptible to reporting slightly inaccurate sizes. I just calculate based on those numbers, if they don't get drawn to what I expect, then odd stuff happens.
|
|
|
|
Post by drbob54 on Jun 10, 2015 10:03:01 GMT -5
George
Interestingly after using the other fonts and reverting back to FixedSys the redrawing of the status bar is much better.
Maybe windows returned different values for height and width of the font.
My thought was that given the status bar and the black edit screen occupied the same area of the screen, that changes to the edit window
which is under the the status bar may generate a lot of redraw messages to the status bar when for example scrolling through data.
|
|
|
|
Post by George on Jun 10, 2015 13:44:27 GMT -5
drbob54: Yes, redraws could cause that. If I don't get an edit window set to the correct size based on what I'm told about font height and width, then I can see where some junk like that would occur. I don't really understand it, but the whole area of window size, dialog size, user area size, graphic area size etc. at times seems like some kind or arcane mumbo-jumbo. Throw in Windows automatically adjusting some of those sizes for the SB, allowing for themes, various sizes of window and dialog frames and my mind goes numb. And I'm doing this without the aid of some visual dialog designer.
George
|
|
|
|
Post by George on Jun 10, 2015 14:29:09 GMT -5
Jo: OK, I at least know the cause of the loop you saw. The rex file you are editing was created via a Clone command (the filename is *.Rex since you have not done a CREATE/SAVEAS etc.) You are also running with ACTION VSAVE, so after your specified interval, an internal VSAVE is performed. This creates a filename for the VSAVE file based on the file being edited. With the *.REX name, we end up with a VSAVE filename with an "*" embedded in it. Oops!
So I have to enhance the build-a-valid-filename-for-VSAVE to cope with this oddball * character.
Oh what a tangled web we weave .....
Temp solution - as soon as you clone a file, do a CREATE/SAVEAS etc. to give it a proper name, or turn off ACTION temporarily.
I'm still looking at your 1st problem, but like you, I can't trigger it.
George
|
|
|
|
Post by drbob54 on Jun 11, 2015 0:55:05 GMT -5
George
I understand you frustration with the whole area of window size, dialog size, user area size, graphic area size etc. at times seems like some kind or arcane mumbo-jumbo.
You forgot the phase of the moon.
I run into the same issues with trying to get the Microsoft tools to play nicely as well.
It interesting that Windows appears to have returned a different more accurate Width and Height for FixedSys when I reverted back to FixedSys after using other fonts.
Wonder if a service pack or a later product installed a 'fixed' version of the FixedSys font.
Anyway the SB and edit window have behaved themselves in recent times.
|
|
|
|
Post by George on Jun 11, 2015 10:18:33 GMT -5
drbob54: Glad this latest version has returned to stability. It's also frustrating in that I never actually found anything I could point at as the cause. I basically re-wrote the code and handled some aspects a little differently, but nothing that should have made a difference. Worrisome.
If I can ever get out of the 'stomping little bugs' mode, I'll package up a real version. It seems we suddenly have an influx of new forum members, all of whom seem to be stumbling on little bugs. I can't complain really, we've been begging for more user involvement for what seems like forever. At times it was like working in a vacuum.
George
|
|
