Cyrus
Tue Feb 15 19:32:11 CST 2005
Carol Crow wrote:
> DO WHILE .NOT. UPPER(ZANS) $'TBHOE'
>
> * WAIT WINDOW N(WROW())+N(WCOL())
>
> DO MyClear WITH 23,1,23,WCOL()
> ============================
> I DON'T THE Modify which group?" Thats where the ERROR Column/Row
> ============================
> @ 23,1 SAY "Modify which group?" ;
> FONT "MS Sans Serif", 8 STYLE "BT"
> nChoice = 0
> @ 23,17 GET nChoice ;
> PICTURE "@*RHT \<Total;\<Black;\<Hispanic;\<Other;\<Exit" ;
> SIZE 1.308,12.667,0.000 ;
> DEFAULT 1 ;
> FONT "MS Sans Serif", 8 ;
> STYLE "BT"
> * @ 23,1 SAY 'To modify, press (T)otal (B)lack (H)isp. (O)ther ';
> +MINFEM+' or (E)xit ' kSayGet ;
>
>
> "Wolfgang Schmale" wrote:
>
>
>>Hi Carol!
>>
>>Since old FPx compute the position of a textbox not in x,y pixel but in
>>Foxel a unit which depends on the screen font you should try to adjust the
>>_screen.font=Samefont_Which_rans_on_FPW
>>_screen.fontsize=sameFontSizeAsInTheFPWApp
>>_screen.scalemode=0 &&foxels
>>
>>
>>--
>>
>>
>>------------------------------
>>
>>Mit freundlichen Gü�en aus der Zigarrenstadt
>>
>>Wolfgang Schmale
>>
>>------------------------------------------------
>>"Carol Crow" <CarolCrow@discussions.microsoft.com> schrieb im Newsbeitrag
>>news:242EDFB3-ABFF-4CCC-AE63-C6A3FB736843@microsoft.com...
>>
>>>An extensive textbox was programmed in fox2.x and I'm upgrading to vfp9.
>>>I get an ERROR row and colum off screen. The program runs fine under vfp
>>>but not as an executable.
>>>
>>>The beginning of the p rog.prgis
>>>
>>>SET READ BORDER ON
>>>STORE .T. TO MORE
>>>
>>>I can't find where the program determines the size of the box.
>>>
>>>What is MORE??? It doesn't show up in the code reference with a
>>>definition.
>>>
>>>I need lots of help with this.
>>>Thanks in advance.
>>>
>>
>>
>>
Ahh MS Sans Serif is the problem here. What you need to do is to change
ALL your font settings to use a non-bitmap font. I use Arial as you can
pretty much be guaranteed it will be there (if it's not the computer is
going to be having more problems than those with YOUR program). This
will make it be the same all the time. Quite often this was a problem
with FPx programs. Switching to Arial solves them in 99% of the cases
(the others are usually bad video drivers, I don't see that so often
anymore).
--
Cy Welch
Senior Programmer
MetSYS Inc
http://www.metsysinc.com