Save Part of Front Panel as picture - sharing VI and asking for advices

Question

Hi,
I use LabVIEW 8.2.1. (DSC&RT),
It is common (at my work) that we want to save some parts of the Front Panel and to add it to the LogBook.
we usually do PrintScreen and then cut the picture to the boundaries we want using 'Paint'.
I have created a simple procedure that makes it easier and the user can now select the boundaries of the picture at the Front Panel.
You can see the 2 VI's attached, (try2.vi is a sub vi of try.vi)
Open 'try.vi' and press 'select boundaries' button and drag the boudaries with your mouse,
after you have selected the boudaries, press 'save picture' button.
I hope there are no bugs.
Originally I have wanted to use drag and drop, but i didn't really understand what is going on behind the scenes
when I used it.
For example - look at the example (at NI Example Finder at LabVIEW) 'Drag and Drop - Multiple Data Types to Start Drag.vi'
(C:\Program Files\National Instruments\LabVIEW 8.2\examples\general\dragdrop\Drag and Drop - Multiple Data Types to Start Drag.vi)
(or via typing 'drop' in at the NI Example Finder search)
1. I don't understand how the 'Drag and Drop Data' (located at the Application Control Palette)
2. I don't understand the inside terminals of the Event Structure of 'Drag Enter' and 'Drop' -
    for example - 'available data names' and 'accepted?'
   where can I get information help written about any of the Event Structure inside terminals?
   (it does not appear in the Context Help when I enter with the mouse)
3. Do you have any comments on the VI  I did ?
4.I am planning to use this VI as a part of Log-In data to a follow-up LogBook Using Mysql as Database and NI sql connectivity toolkit,
   so users will be able to insert information to the LogBook from the Front Panel, and attach pictures of the Front Panel.
  Did anyone here has performed anything similar ?
If you send me corrections of someting or any other NI item, please send it in a version that I can see it (I use Labview 8.2.1 DSC&RT)
Sincerely Yours,
Amitai Abramson.
Attachments:
try.vi ‏67 KB
try2.vi ‏23 KB

Answer 1

There are examples that come with the database connectivity toolkit so you are going to have to be more specific about your question. Whether you call it a logbook or something else, it's still a database and a database write is a pretty generic opertation. If you need help in the design of the database, then you should say that is what you need.
The event data is going to change depending on the event and the type of control. Again, do you have a specific question?