search

jacobson3 / VI-Peek

MIT License
4 stars 3 forks source link

Potential Issue with using DQMH #13

Closed qalldredge closed 2 years ago

qalldredge commented 3 years ago

This becomes a problem when creating LabVIEW IDE add-ons no matter what framework you use. There is the potential that you lock up classes or libraries of the framework. This is due to the libraries being used in your instance as used by the add-on tool and also in use by a developer using your tool while developing their own code using those libraries.

There are two workarounds:

  1. Don't use the frameworks/libraries
  2. Make sure when your tool is deployed (via a package or otherwise) that a different namespaced copy of the framework code is installed for use of your tool.

I have had to remove instances of Actor Framework and MGI's Panel Manager from some of my IDE add-ons for this reason.

jacobson3 commented 3 years ago

This is good to keep in mind but do you think that this will even effect people using the DQMH framework? My understanding is that this would cause the DQMH classes to be locked to editing but is that something that DQMH users would need to do? I'm not a DQMH power user but from my experience these classes just sit in my dependencies so I'm not sure being locked is an issue.

qalldredge commented 2 years ago

You are right. This should only cause locking of the underlying DQMH classes. Everything else should be fine.

jacobson3 commented 2 years ago

I'm in the process of creating a package build and I've added DQMH as a dependency so those files should be present when installed as well.