-
Version 2 Subroutine Window Fetch Handle, Integer, Public, Returns Handle to Control Successfully, 0 Fails to Return
Parameter Parent window handle, integer, can be empty, if it is a top-level window handle, please leave it blank.
Parameter sub-window handle, integer, nullable, if it is a top-level window handle, please leave it blank.
Parameters Window class name, textual, nullable, window class name.
Parameters Window Title, Textual, Nullable, Window Title.
Returns (findwindowexa text (parent window handle, child window handle, window class name, window title)).
Version 2dll command findwindowexa text, integer,"user32", "findwindowexa"Public.
Parameter Parent window handle, integer.
Parameter subwindow, integer.
Parameter class name, textual.
Parameter Title, Textual.
-
Define the variable x copy window component ( Startup window. button 1,x) is then in the ** of button 1: local variables:
event components; Button locals: the title of the get; Textual **: Event component = take the title obtained by the event component () = event component. Title.
-
Subroutine button 1 is clicked.
Local Variables Event buttons, buttons.
Assignment (event button, take event component ()).
Debug output (take the component name (event button)).
-
It doesn't seem to be very good, you can just use the copy component.
-
Method: Re-open Easy Language, but add a button.
1 Please hold down the "Shift" key on your keyboard and don't let go2 Then click to open the Easy Language Development Tool (that is, the Easy Language icon on the desktop and start menu).
3. Finally, when the language is fully opened, these windows will revert to the default opening.
In addition, in the easy language menu, check the box - Toolbar - "Window Component Box", and it's OK.
-
Click on the three horizontal line buttons above your screenshot!
-
Click the figure-three button on the top of the component box.
-
Tap this (**the leftmost one).
-
.Version 2
Subroutine tab 1 Left mouse button is pressed, logical. Parameter transverse position, integer type.
Parameter longitudinal position, integer type.
Parameter function key state, integer type.
Windows 2Box 1Contents Launch window. Label 1Title.
-
What you said about window 1 and window 2 are two independent easy programs or two windows in an easy program, if the latter can be implemented using global variables, then it is estimated that you need to get the memory address, I haven't done it but think so.
-
There is no method to get a component name yet.
Components can be taken. Tags But first you need to mark the component as well as the component name, as follows: You need to click on the transparent label to trigger the event Transparent label"Name"Yes"Log 1"What about the components"tags"too"Log 1"(Tags are set in the component properties).
Build one first"Global variables"
Global Variables are temporarily selected, transparent labels.
Transparent Label Trigger Script:
Version 2 Subroutine Log 1 Left mouse button is pressed, logical. Parameter transverse position, integer type.
Parameter longitudinal position, integer type.
Parameter function key state, integer type.
Temporarily select Fetch Event Component(s).
Onboarding (log window, startup window, true).
Version 2 Subroutine Detailed Bet Window has been created.
Local variable tags, textual.
Mark Tentatively selected. tags
Infobox (.)"The current event name is:"+ marker", 0, ,
-
It's okay to set the prompt property haha!!
-
With a shake of your little hand, the currency is in hand!
-
It's very simple, click on the button component, and the properties will appear in the left toolbar, and you can modify the button name. The same goes for other components. If you have to study the source code of the language textbook and study more, you will understand. Take a look at the picture:
-
Object. Take the window handle ().
Label 1Take the window handle ().
Frame. Take the window handle ().
Button. Take the window handle ().
-
The name of the component. Take the window handle ().
-
Pass from the parameters, customize the parameter name, and set the parameter type box.
In this way, when others call it, they will pass the box group name in.
-
Do it by looking for the window handle.
-
Hello Lonely 0562, for example: Advanced**1Get the window handle () This takes the high-level window handle (any component can be seen as a window, this is the high-level handle, not the handle of the window where the window is located).
Call format: integer object to get window handle () system core support library - > window.
English name: gethwnd
Remove the window handle (i.e., hwnd) of this window or window component. This command is a member of an advanced object.
OS Requirements: Windows
Hello, this problem is easy to solve.
There are several ways to replace component names with variables, but I'll give you two of them. >>>More
I'm not going to do it, but I'll give you an idea:
List the names of all the files first, then use the charms to sort them and correspond to them. It's a simple problem, but it's too complicated to implement. >>>More
Hotkey. Registration (Tab 1.)Take the window handle ()0, F1, > register F1 >>>More
If you don't change the program, it won't change. Be careful not to confuse the concepts of system and procedure. The QQ** you wear with the SkinSharp program will not change because your computer** is changed to "classic".
Doesn't the key wizard come with a footstep?,There's this function.,Find it yourself.。