Mark, thank you for your presentation, it was very informative and well delivered.
One correction to the content, in Part 2, Dynamic Event Challenge, there is an image with a note in the "Mouse Move" event that says in this event, the "coords" terminal give you the number of pixels from the top left of the front panel, not the picture control. This is actually incorrect, in a "Mouse Move" event, the coordinates are give relative to the front panel grid. By default, the upper left corner of the front panel window is 0,0 because the grid is aligned in a new VI, however, once you scroll left or right, the grid will change. In this example code, the horizontal 0 for the grid has been shifted so that the picture control is half over it.
Additionally, LabVIEW uses what I believe is Linux standard screen coordinates where 0,0 is upper left and to go right is positive and to go down is positive. This means in this example, if you probe the coords in the mouse move event you will see a negative vertical value for clicks above the darker grid line running through the middle of the picture control horizontally and positive coordinates for the vertical value for clicks below this darker grid line.
Regardless, the posted solution works by a simple subtraction of the picture's position coordinates from the mouse coordinates since both are relative to the grid. However, this can get really confusing really quickly if you starting throwing in coordinates that are absolute to the screen or to the frame rather than the labview grid, especially if you later move the grid and don't realize it. This has confused me before.
