Can I create my own .cbx file or modify a current .cbx file?

[Ollie]

What I would like to do is create an object that will give me a DOUBLE Action Verification message (Are you sure? YES! Are you REALLY SURE? YES!) I'm doing this already with a cloggy of pop-up messages, and wanted a CLEANER and Easier way to do this. My thought was to modify the current PUSHBUTTON -- logctrl.cbx file. Or create a similar one. Any thoughts???

[Khalid]

National Instruments provides (for a price) an Object Developer Toolkit for Lookout with which you can create your own CBXs. However, this toolkit is mainly for developing driver (I/O) CBXs. It does not support the creation of displayable objects like the one you want.

So, an alternative may be to create a regular ActiveX control.

Regards,

Khalid

[Ollie]

Thank you for your timely response. I posted a similar question back in March here:

http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=5065000000080000000C3E0000&USEARCHCONTEXT_CATEGORY_0=_9_&USEARCHCONTEXT_CATEGORY_S=0&UCATEGORY_0=_9_&UCATEGORY_S=0

I followed the suggestions but my customer is continually adding sites. And the number of pop up windows and push buttons grows and grows. My hope was to find someone that has an EASY solution or has written something already.

[Khalid]

If this is the case, have you thought of using the Aggregate object? You can "create" your own Object out of the existing pop-up windows and push-buttons once and for all and keep using this as an "Object" in future.

Here's a snippet from the Online Help on the Aggregate Object:
The Aggregate object is a way for you to create a collection of Lookout objects, already connected and configured, and use that collection multiple times as an element in your processes.

Create an aggregate by creating a Lookout process and saving the process as an aggregate definition file, choosing which of the object parameters and data members to expose when aggregate is used in another process. Then use that aggregate definition process in other processe
s by creating an aggregate object that uses your aggregate definition as its source. ...

[Ollie]

That sounds like a very viable solution, but lets step back to the Active X control. I'm not an ACTIVE X programmer, but have a couple at my disposal. What do they need to interface their ACTIVE X stuff to Lookout? Is there any documents that describe this process?

THANK YOU VERY MUCH FOR YOUR TIME!!!

[Khalid]

There sure is a document:

http://digital.ni.com/softlib.nsf/954feaeea92d90918625674b00658b83/26166a48f59026a986256bbc0053aafd?OpenDocument

Actually the above is an addendum to the Object Developer's Toolkit I referred to earlier (hence not a free download). This addendum explains how to "Lookoutify" an existing ActiveX control to work with Lookout. That is, ideally, any ActiveX control would work with Lookout .. this document tells what needs to be tweaked in case the control isn't working properly.