Link describes custom palette, but I don't have the DLL mentioned

[InternationAL]

Please refer to the following link:  [link removed]  Supposedly, I can create a custom palette in DIAdem using a DLL, custplt.dll, which I don't have access to.  Can anyone follow the directions given at the link, with success, and offer me a copy of the DLL mentioned?  If not, can anyone offer another solution to accomplish roughly the same thing as what is being described?

Also, if this can't be done, and the DLL never existed, then where did this info come from?  Was it in DIAdem 9, and now it's gone from 10?

If I have to write my own GPI extension, I would like to do that, but what do I need to do this, and is there a good way to get started?

I am using DIAdem 10.1, by the way.  If I have left anything out that would be of assistance in answering my question, then please let me know.

[InternationAL]

Oh, by the way, can anyone offer any assistance on what each of the bundled extensions does?  I see a number of DLLs are already included with DIAdem by default.  I am really interested in finding out what the Excel extension does.

[Brandon_V]

InternationAL,

I'm currently looking into the problem with this missing GPI DLL and will post on this forum as soon as I find where this DLL is located. You can create DLLs using the GPI Wizard. This requires Visual Studio C++ 6.0 since this is what GPI technology is built on. Since you have 10.1, unless you like using C++ (GPI is not the easiest to program for), you have many other options for using your code in DIAdem. As far as the documentation for provided GPI DLLs, I will also post back here as soon as I am able to find this documentation

[InternationAL]

So, you can't use VB .NET to do the programming?  I am more familiar with that than I am with C++.  Isn't .NET setup so that you can program in any language, and the resulting compiled code is the same?

I sure would love a tutorial somewhere on GPI, just to see how much I really don't want to program for it.

Thanks for the other link, I will check it out.

[Brandon_V]

There are no tutorials for GPI because it has about 3000 extra lines you have to add to it and is only compatible with C++ 6.0. This is before .NET, so you can not use the .NET framework for this. The wizard is provided so that you can create GPI without spending hours adding these 3000 lines needed.

[Twigeater]

Hello Brandon!

What you say is not completly right. The GPI can also be used with Delphi (Pascal). The interface files can be found in the GPI documentation directory. It is a little more work because there is no wizard available. We developed a class wrapper wich makes it easy to use. In general every programming language wich is able to export standard C functions can be used.

Matthias

[InternationAL]

Hello!  So, what interesting customizations of DIAdem have you come up with that couldn't be pulled off using "normal" methods?  I am trying to understand the capabilities and purpose of GPI extensions.  Have you been able to make non-modal forms/dialogs or additional toolbars for DIAdem, or is this a possibility?  As I understand it, "normal" customization of DIAdem allows you to add menu items, but doesn't allow for additional toolbars or non-modal interaction with the user via scripts.

Thanks everyone for the replies!

[Twigeater]

Hello InternationAL!

In our main GPI extension DLL, used in every project we realize, we have more than 200 commands and more than 50 variables. They cover different areas (abstract):

• Dynamic variable allocation
• Macro variables
• Variable helper commands (e.g. sorting)
• Non-modal info dialog
• Non-modal 'flying' dialog
• Context menu
• Resource DLL access
• Extended logging features
• Fast Excel binary data export
• Several DIAdem helper functions (e.g. bring-to-front)
• Better channel manipulation commands (e.g. fast&flexible channel sort for numeric&text channels)
• Script Watchdog
• Full windows help access
• INI and registry access with caching
• SUD helper commands
• Windows API access
• ...

Before it was possible to program DIAdem with VBScript GPI was the only way to extend DIAdem. Today some of the features are outdated because you can replace them with automation servers, etc.. But a good thing is that GPI dlls need not to be registrated wich is not possible on every computer and there are still some features only possible to be implemented in a GPI DLL (e.g. fast data access). It is not possible to extend the DIAdem GUI itself - no additional toolbars, etc..

BTW: I think that we inspired the article you started with, by the non-modal 'flying' dialog we developed in 2001.

Matthias

[InternationAL]

So, are you the proud owners of the missing DLL mentioned in the article?  Do you have a copy?

It seems like the DIAdem GUI might be "manipulated" by adding these floating palettes.  It would be the closest thing to adding a toolbar, I guess, and would be what I am after.  I want to implement a non-modal dialog.  If I could get that floating palette to work, I would be happy.

If it is not too much trouble, I would be interested in the list of features implemented by you in a GPI extension that is not "outdated".  In other words, here is the list of things we do that can only be done via a GPI extension, and here is a list of things we could do with a GPI extension, as well.  That way, I could figure out if I need to pursue this very far, or not.  It wouldn't have to be an exhaustive list, either.  Just a top five of the things you sure are glad you have GPI extensions for.  Then  I could figure out whether I need to learn this or not.

If something can today be done in script, or via some other more documented means, than learning GPI extensions wouldn't be motivated by that.

Is everything you listed only doable with GPI extensions?  I guess not, since you said some of the items are "outdated".

Thank you so much for all the information you have provided.  I appreciate it.

[Brandon_V]

Al,

I was able to find the source of the problem, somehow the files attached to that particular document got lost on our webserver and were no longer being linked. I have attached the file and will be editing this document so that this does not happen again, my apologies for this occurance.