When I use the STK X controls on an HTML page, my browser pops
up the following warning:
What does it mean? What can I do about it?
Your browser is warning you that the HTML page uses some ActiveX controls that are not marked as safe for scripting/initialization. The STK X controls are not marked as safe because they can write files (STK scenario files) on the user's computer; thus AGI cannot mark them as safe for scripting under the definition set forth by Microsoft.
There are two courses of action you can pursue to avoid this warning:
I have two projects opened in two instances of my development tool IDE with the STK X controls opened in the designer. When I run my application STK X fails to find a license. Why?
STK licensing limits you to running simultaneously two instances of STK X. A license is checked out each time an STK X control is used in a designer. Thus, for example, you will not be able to obtain a new license if:
To make certain STK X finds a license when you run the application, it is suggested that you close the designers to free the license.
My PowerPoint presentation uses STK X globe and/or map controls. After I use the mouse to manipulate the control the Page Up and Page Down keys can no longer be used to navigate to the previous or next slide. Why?
The STK X control has the focus and receives all keyboard input. You need to switch the focus back to the PowerPoint slide. Click once on the slide background and then use the keyboard.
Are the STK X components and controls thread-safe?
The STK Engine components and controls use the apartment threaded model. Therefore, the STK X application object, the STK Object model root, and the map/globe controls all need to be instantiated in the same thread. For example, if the controls are used in the UI thread, everything needs to be instantiated in the UI thread.
I sometimes encounter problems using the Application property of the Globe and Map controls in Microsoft Excel? Why? How can I avoid these problems?
Excel automatically adds some pre-defined properties to all Active X controls. One of these properties is named Application and hides the STK X Application property. To access the STK X property. use:
Dim stkxApp As AgSTKXApplication
Set stkxApp = Me.AgUiAxVOCntrl1.Object.Application
I used a previous version of STK X in a Microsoft Office document (Word, Excel, PowerPoint, etc.). That document does not work now that I have upgraded to the new version of STK X. How can I fix this?
When a control is inserted into a document, Microsoft Office creates a cache of the type library containing the control. If this cache is out of date, some new or changed properties or methods may not be accessible. You need to delete the cached type library.
For PowerPoint the file is called STKXLib.exd and is located
[%TEMP%\PPT10.0]. See Microsoft Knowledge Base
Articles 158875, 185473 and 290537 for other office
What should I be aware of to ensure the best performance of my STK X application?
There are several ways you can significantly improve performance, including these:
[ConControl / VerboseOff].
AgExecCmdResultcollection (instead of the Item property) to avoid unnecessary round-trips through marshalling.
I would like to use several Globe and/or Map controls in my application and load a different scenario in each control. Is that possible?
No, only one STK X engine can be embedded in one process. Therefore only one scenario can be loaded at a given time in one application. Each control acts as a view of the common scenario.
Can I use both the STK X controls and the STK Viewer control in the same process or application?
No, that is not supported.
Can I mix STK X controls from different versions in the same application?
No. Only one version can be used in one process (because they share the same DLLs).
How do I set the VendorID property properly?
This property must be set when using a STK Engine deployment license.
When using a deployment license with a VendorID specified, the VendorID value must be set as early as possible and before performing any work with the engine. It can be set once at runtime using the AgSTKXApplication object on a STK Engine application startup. This is the recommended method. Alternatively, it can also be set at design time through the property exposed on the various engine controls. If you are setting it on the controls at design time, it is required that this property be set on all controls.
STK 11.2.1 Programming Interface