From Xojo Documentation
- 1 IPC Socket
- 2 Note Player
- 3 Shell
- 4 Serial
- 5 Server Socket
- 6 Spotlight Query
- 7 TCP Socket
- 8 Thread
- 9 Timer
- 10 URL Connection
- 11 UDP Socket
- 12 Object
- 13 Xojo Script
These are the controls and classes in the Controllers group of the Library.
The controls in this section are all non-visual. They do not display on the Window in the built apps and the user cannot see or interact with them. When added to a Layout, they appear on the Shelf area.
Adding these controls to the Layout is merely a convenience to give you easy access to their event handlers. Although you can also create these controls in using the New operator you will not have access to the event handlers unless you first subclass the control (and access the event handlers there) or use the AddHandler command to map event handlers to methods on the window.
You can also add just about any non-visual class to a layout by dragging the Object control onto the layout and changing its Super to the class you want.
The IPC Socket performs interprocess communications between two applications running on the same computer. Use it to send and receive messages. Like other sockets, the IPC Socket control displays an icon when placed in a window in the Window Editor but has no interface.
Plays musical notes. Refer to NotePlayer in the Language Reference for a list of available instruments.
- The number of the musical instrument to play. Refer to the Language Reference for a list of the available instruments and their values.
- Plays a note using the supplied pitch and velocity.
Provides a quick way to run Unix or DOS shell commands.
Although the Serial control displays an icon when placed in a window in the Window Editor, it is not visible in the built application. It is designed only for executing code to communicate via the serial port. For more information, refer to the UserGuide:Serial Devices topic.
The ServerSocket class enables you to support multiple TCP/IP connections on the same port. When a connection is made on that port, the ServerSocket hands the connection off to another socket, and continues listening on the same port. It includes the ability to replenish its supply of TCPSockets as connections are made. Without the ServerSocket, it is difficult to implement this functionality due to the latency between a connection coming in, being handed off, creating a new listening socket, and restarting the listening process. If you had two connections coming in at about the same time, one of the connections may be dropped because there was no listening socket available on that port.
Used to perform Spotlight searches on Mac. It does nothing on other operating systems.
Used for executing code to communicate with other computers on the Intranet or Internet using TCP/IP.
The Thread class is used to have processing run in the background, which is very useful way to keep the user interface responsive while a process is running.
The Timer executes some code once or repeatedly after a period of time has passed.
A URL Connections supports web communications to URLs.
You can use this control to send and receive requests to web services and other web-based APIs.
The UDPSocket supports communications via a UDP (User Datagram Protocol) connection.
UDP is the basis for most high speed, highly distributed network traffic. It is a connectionless protocol that has very low overhead, but is not as secure as TCP. Since there is no connection, you do not need to take nearly as many steps to prepare when you wish to use a UDP socket.
UDP sockets can operate in various modes, which are all very similar, but have vastly different uses. Perhaps the most common use is “multicasting.” Multicasting is a lot like a chat room: you enter the chatroom, and are able to hold conversations with everyone else in the chatroom.
Use this generic object to add any class to the layout so it can work as a non-visual control, giving you easy access to all its event handlers. Drag the Object to the layout and then change its Super property to your actual class name.
The XojoScript control allows the end user to write and execute Xojo code within a compiled application. Scripts are compiled into machine code.
You pass the code that you want to run via the Source property and execute it by issuing the Run method.