question

1. The Control Point and Decision Point classes each implement the onDrag() method in order to fire code when being moved. That custom onDrag() code loops through the interesting objects in the model (conveyors for decision points and agv paths for control points) to determine whether to set the objects position to "snap" to those objects. This is all custom code, and you would also need to write custom code to get this type of behavior. You can use the draginfo() command in the onDrag() method to get information about the mouse drag operation.

2. You can hide the sizer cones by calling setpickingdrawfocus() from the onDraw() method of your object, using the OVERRIDE_DRAW_ALL option to "cause FlexSim to not draw any sizers or boxes around the object."

You can use the Mesh API to draw whatever you want. See mesh.h in the Module SDK. The Module SDK Documentation "ExampleModuleClass.html" Snow Processor tutorial shows an example of using the Mesh class from a module. You can also find FlexScript examples of using the Mesh API here on Answers, such as:

How to use mesh API?

How do I add a texture to a mesh when using the mesh API

The principles of using the Mesh API are the same between C++ and FlexScript, but the syntax is slightly different.

3. Those events are generated by the AGV Network and Conveyor System objects respectively for Control Points and Decision Points. The code controlling what is happening when an item is on a conveyor or using the AGV network is written on those objects, so they use that data to fire events at particular times (related to the positioning of those objects). This is what you have to code up in order to "create a new object." You have to tell it when to fire triggers that are important relative to your object and its logic.

The checkCollision() method is related to the Collision tab on task executer objects. Almost no one uses that feature. It is an old, slow, ticker-based system that is almost never used because there is almost always a better, more efficient way to calculate important events instead of doing collision detection every X time units.