tushar

In VB if i write my own ActiveX Control then in addition to Properties and Methods i can Define my own custom events. is there any similar thing availale For X Controls written in LabVIEW if yes then how can i write my custom events. i dont want to generate the event based on instance of Xcontrol. but i would like to Embed an user event in Xcontrol which i can handle in event structure outside XControl Thanks

I want to get the names of all the items in function palette and controls palette as it appears on the palette. the paletteAPI is useful for getting many item names but it returns the code for inbuilt functions. is there any way that i can put all the item names (Exactly as they appear on the palette) in a tree structure

QUOTE(sachsm @ May 15 2007, 09:14 PM) please see this thread on ni forum http://forums.ni.com/ni/board/message?board.id=170&message.id=241813#M241813' target="_blank">http://forums.ni.com/ni/board/message?boar...=241813#M241813

While developing various applications we found out that error handling is one of the most important(at the same time one of the most ignored) task. so we decided to develop some modules which will allow us to configure the handling methods after develoment we think that this library can be useful to everyone, hence we are making it public please feel free to give your feedback, bug report, improvement ideas etc... you can also Email me at tushar@vispune.com Download File:post-2027-1166519779.zip

Hi All i am new to LabVIEW and i want to wet my feets in VI Scripting field by executing this project. i hope i ll get help from u guys. I want to develop an utility which will help programers to debug their program(specially program which have lot of parallel loops and where it is difficult to track the exact location of generation of error). this utility will be a single VI which user will place at several locations in his code. and this VI will basically work as active probe (user can change the probe value) below is the brief spec list. 1.This Utility will have Error in, Error out terminals and preconfigured mode(Mode settings can be stored in ini file so that even exe can be executed in debug mode to track the problem) 2.As soon as any of the instance of this VI Executes LabVIEW Program should pause temperarily(Even VIs in other parallel loop); block diagram of perticular VI should be poped up and the instance of Mr Debug should be flashed (similar to the thing that happens when you search multiple instances of VIs and press ctrl+G)and this utility will pop up a panel so that user can alter the value of error at perticular point. 3. After user alters the value of error in Mr Debug panel; program should resume its operation 4. User should be able to add an error even if their is no error currently (so that he can see his program will respond properly if perticular error occurs) 5. general options like log to file etc should be available 6. one tool should be developed which can remove all instances of Mr. debug from the VI and join the error wire appropriately.(compacting code before release) 7. if Mr. Debug instances are placed in parallel loops not more than one instance should be flashed(Or panel poped) simultaneously. please let me know how we can make Mr. Debug Even More attractive. now lets come to the problems i am facing. 1. I can flash the objects on block diagram using obj highlight mode but it works only if VI is in edit mode(but surely there is a way as we see simiar thing when LabVIEW asks us to continue or stop program when unhandled error occurs) 2. can we pause the execution of VI in between execution and still keep the subVI placed in it running(Our Mr. Debug VI)) 3. If there are multiple instances of Mr. Debug VI on a digram then how to determine which icon on the diagram should be flashed in parent VI please guide me how can i proceed. also please let me know whether we can do anything to make it better. can we do anything through which we can replace the LabVIEW built in Error handler with Mr. Debug(So programmer can use this facility without dropping a single instance of Mr.Debug in code) Thanks Tushar Jambhekar