🚀 go-pugleaf

Dave -
 
  To echo what Jesse has said, I can think of a scenario that might cause
problems with changing the fPrefersOutline setting of the TTEView for some
applications. Consider an application that uses a dialog box with an edit text,
initially empty, that uses Times 12 font. Times is not used anywhere else in
the application. The TEditText is set to prefer the outline font. The user
enters text in the edit text, and clicks the OK button to exit. There are no
other edit texts in the dialog; for that matter there are no other
target-eligible views in the dialog.
 
  As the application currently stands, the text for the edit text is imaged
using bitmap Times 12. However, with the change, the text will be imaged using
TrueType Times, scaled to 12 point.
  The difference is one of memory usage in the system heap. Remember, Times is
not used anywhere else in the application (and assume for argument that it is
used in no other applications). Before the patch, the memory usage in the
system heap was 7K (for the Time 12 bitmap); after the patch, it is 67K (for
the Times TrueType definition).
  It is important to note that, since the edit text is initially empty, the
TrueType font is not loaded until the user starts to enter text in the dialog.
(Check the code).
 
  Could this cause problems? Possibly. Frankly, I doubt it. The memory
difference (60K) is too small to really be a problem. The problem could easily
be fixed in this instance. Is it really an error with the patch? I would argue
that it isn't, but, and this is the important part, it is a change in the side
effects of using a TEditText.
 
  Granted, this is stretching it. But this is just off the top of my head.
Maybe it will happen, maybe not. Do you know of any way of checking without
testing the code?
 
Bob
 
 
Bob Hablutzel
Hablutzel Consulting
ALink: B.HABLUTZEL
Phone: 708 328 0130