.DLX Files Where are They!!

[designnewz]

I am currently using Snap Journaling and When I create a script AND RUN FOR first time the script generates a DLX file. Does anyone Know Where the DLX File would reside on any computer. This may help me when Different groups that are in Play with this specific Script.


When you use the BlockStyler to create a dialog, a separate file (.DLX) is created, and stored in that file is a lot of info about how the dialog should look when launched. In addition, in the code that calls the dialog into existence, there is something called an initialize callback which is a function that lets you control how the dialog will be displayed, and it will override what was stored in the .DLX file. In that scenario, when your apply callback runs, it also runs the initialize callback to reset any of the values in the dialog that you program it to reset.

When using SNAP to create these dialogs on the fly, there is no initialize callback, and the apply callback just takes whatever actions you tell it to, so nothing automatically resets the dialog. The code in New() only runs the first time you display the dialog - that is, as long as the dialog remains displayed, it never runs again. After you exit the dialog, then when you run it again, New() runs again.

 

[PSI-CAD]

Hi

I don't use SNAP but I know that in vb, the dlx file must be stored in the folder "startup/application".


Regards
Didier Psaltopoulos

http://www.psi-cad.fr

 

[designnewz]

Found the DLX files a lot of information. Found under my local under AppData Siemens

 

[BubbaK]

You don't use SNAP *instead* of VB. They are apples and oranges. SNAP is just a library, like NX/Open. VB is a langauge, like C#, or Java, or Python. You write VB code (or C# code, or whatever) that calls functions in the SNAP library.

The DLX file that you create with Block UI Styler can be placed anywhere you like. But then, when you reference it, you have to use its full path name, not just the file name.

 

[BubbaK]

There are (at least) two ways to create Block-based dialogs for use with SNAP.

First, you can use a Snap.UI.BlockDialog. This is not very much different from an NXOpen.BlockDialog. You use Block UI Styler to design the dialog, and this produces a DLX file that you reference in your code. You determine the location of the DLX file when you do a "Save" operation in Block UI Styler. You can save it anywhere you like, provided you reference it using its full pathname.

Alternatively, you can use a Snap.UI.BlockForm. You construct one of these by calling various functions at run-time. You don't use Block UI Styler, and (as far as I know), no DLX file is created. There is no Initialize callback because you initialise the dialog in the code that creates it.

If you have lots of time and energy, you can even construct DLX files by hand, with a text editor. That way, you can have standard block-based dialogs without paying for a Block UI Styler license or a SNAP license. But, if your time is at all valuable to you, I wouldn't recommend this approach.

You say you found some DLX files. I'm not sure what these are, but I'm pretty sure they don't correspond to any Snap.UI.BlockForm that you created.

Block-based dialogs are explained pretty clearly in the "Getting Started with SNAP" guide that comes with the standard NX docs.