Post by (X) on Mar 2, 2024 4:44:22 GMT 1
LText: What is it?
From the Help Doc...
LText Control
Purpose
Creates a left justified-text static control in the current active form, window, or dialog.
Syntax
LText text$, id%, x, y, w, h[, style%]
text$:control text
id%:control identifier
x, y, w, h:iexp
style%:the control styles
Description
LText creates a rectangle with width w% and height h%, whose upper left corner is at the coordinates specified in x% and y%.
The text specified in text$ is displayed in this rectangle left justified.
WS_TABSTOP and WS_GROUP are available as style elements.
style Specifies the control styles.
This value can be any combination of the following styles: SS_LEFT, WS_TABSTOP, and WS_GROUP. If you do not specify a style, the default style is SS_LEFT | WS_GROUP.
Creates a control without an OCX wrapper; so it and cannot be handled using properties, methods, and event subs. When used in a form the WM_COMMAND and WM_NOTIFY messages should be handled in the form's _MessageProc sub.
Example
Purpose
Creates a left justified-text static control in the current active form, window, or dialog.
Syntax
LText text$, id%, x, y, w, h[, style%]
text$:control text
id%:control identifier
x, y, w, h:iexp
style%:the control styles
Description
LText creates a rectangle with width w% and height h%, whose upper left corner is at the coordinates specified in x% and y%.
The text specified in text$ is displayed in this rectangle left justified.
WS_TABSTOP and WS_GROUP are available as style elements.
style Specifies the control styles.
This value can be any combination of the following styles: SS_LEFT, WS_TABSTOP, and WS_GROUP. If you do not specify a style, the default style is SS_LEFT | WS_GROUP.
Creates a control without an OCX wrapper; so it and cannot be handled using properties, methods, and event subs. When used in a form the WM_COMMAND and WM_NOTIFY messages should be handled in the form's _MessageProc sub.
Example
LText "Filename", 101, 10, 10, 100, 100
Do : Sleep : Until Me Is Nothing
Q: If you put a LText, CText or RText statement in a loop, will it slow down your program?
A: Yes !
A: Yes !
// Syntax:
// LText text$, id%, x, y, w, h[, style%]
The 'Text' statement does not seem to suffer from this malaise.
// Syntax:
// Text x!, y!, sexp
I wonder if looping multiple LText statements is like creating a "Label control" over and over again thus taking up more and more resources?
I must have been really over-tired when I wrote this code...
It now seems obvious that LText and Text statements are NOT the same !