×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

API, ActiveX, and DLL plugins

API, ActiveX, and DLL plugins

API, ActiveX, and DLL plugins

(OP)
In my current project, I decided to make an custom activeX
control as a 'replacement' FeatureManager. (Its a custom treeview that allows numeric/boolean/listbox inputs within the tree, and I'll be putting it in a newly created FeatureManager Tab)

I currently have all the code that interfaces the ActiveX with my SW API code bundled into the ActiveX, but noticed a considerable lag in SW feature generation/rebuild time from when the API-related code was run as a SW macro (In Process).

The obvious fix here is to make the VB code as a plugin DLL,
but what status does that leave the activex code?
If the activeX code is started from an in-Process .DLL, is the code inside the activeX also now running in-process?

Will I be able to access variables stored within the activeX code? And what about events?

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources