(This usage is consistent with the FoxDOS feature). As best I can tell (having no documentation available except the old 2.x documentation), the pairs that pertain to button coloring under VFP 8 and VFP 9 are pair #9 (which pertains to an enabled button) and #10 (for disabled buttons). The color pair list contains up to 10 "color pairs". The parameter for the COLOR clause is a "color pair list". But now, under VFP 8 and 9, you gotta use it if you want the button to look "normal". The COLOR clause is ignored, if present in the push button command, under FoxPro for Windows 2.x and under VFP 3 through VFP 7. The COLOR clause was originally supported for push buttons for use under FoxDOS. The solution is to include the COLOR clause in the command. In a case such as we have here, when Microsoft implements a modification to the way that the command works, this level of documentation is decidedly unhelpful.) If you go into the FoxPro help and/or and ask about the documentation just says "supported for backward compatibility, use new stuff instead". (Microsoft deprecated the documentation for the commands years ago. However, Microsoft did provide a solution to the problem, which, as far as I can tell, is not officially documented anywhere, but which has been mentioned by Microsoft personnel in a few places, such as usenet newgroups. The change in appearance is apparently due to the implementation of "XP themes" in VFP 8. However, the same source code, compiled under VFP 8 or VFP 9, produces buttons with a white background, which look crummy. Normally, this is black text on a light gray background for an enabled button, and dark gray text on a light gray background for a disabled button. When the SPR program is compiled under FoxWin 2.x or under VFP 3 through VFP 7, the push buttons take on the default Windows color scheme. One variety of the command creates one or more push buttons (generally known in VFP as "command buttons"). Of course, the program could also be hand-coded, rather than being generated, but that would be the exception.) (The program generation process normally produces a program file with filename extension "SPR". More specifically, it pertains to a screen generated by FoxPro for Windows 2.x (not FoxDOS) that is then compiled using VFP 8 or VFP 9 into an executable. Till next time.This topic pertains to running a screen program that contains the old (pre-VFP) FoxPro 2.x commands READ CYCLE, etc.). Those are the two powerful input validation functions in Visual FoxPro 9. Double-click the OkButton then enter the following:ĥ. The following example demonstrates the capability of ISDIGIT function:Ĥ. ISDIGIT can be entered in any capitalization. Expression can be a variable, a number, or a control. Just like the ISALPHA function, the default value of is numeric function is false and it returns true whenever the contents of the expression is a numeric value.ġ. It works like ISNUMERIC function in PHP wherein it allows you to test whether the input is a numeric data. Double-click the control named OkButton then enter the following codes:ĥ.Press F5 to test our sample application.Īnother useful input validation function in Visual FoxPro 9.0 is the ISDIGIT function. Click Start>All Programs>Microsoft Visual FoxPro 9.0.Ĥ. To see ISALPHA in action, follow these steps:ġ. ISAPLHA can be entered in any capitalization. Expression can be a variable, a text, or a control. It is very helpful in filtering illegal inputs:ġ. By default, ISALPHA has a false value and returns a true value when the Expression is a string data. ISALPHA function is one of the powerful functions in Visual FoxPro 9 that can be used to test if the inputted data is a string or character.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |