Hi Neil,
[quote user="Neil McGuire"]Sorry if this ends up being several questions. If I need to split it up into a couple of different threads, I can do that.[/quote]
I agree with Jon it's better to start with separately discussed simple questions, on the other hand the starting more general discussion, that can help to evaluate basic ideas and directions, is not bad first step.
[quote user="Neil McGuire"]I'm trying to create an MDL app[/quote]
It's a bit confusing terminology, because historicaly "MDL" was used as a name for different things, but I guess for the most of people "MDL" mean native code. In CONNECT Edition era "MDL" is used as a general naming for group of technologies or APIs that MicroStation offers. In my opinion it's better to explicitely use "MicroStation addin" or "managed code" if you plan to use C# and "native app" if C++ will be used.
[quote user="Neil McGuire"]that will run in the background while the user has a .dgn open[/quote]
MicroStation has been event driven environment from early versions. So to use "run" is probably not the best word, because MicroStation applications (both managed addins and native applications) are loaded, but they not "run" for the most of the time, they are loaded and waiting to be activated by some event (key-in, internal command, MicroStation event etc.).
[quote user="Neil McGuire"]That seems to work, if I add it to MS_DGNAPPS ... Like adding a file to `MicroStation\config\appl`?[/quote]
It seems there is a lack of knowledge how MicroStation variables works and also how MicroStation application works. I think you should split the development (and relevant discussions) into more steps:
- To ensure your applications works fine and provides required functionality when loaded manually by a user.
- To define when the applicatin should be loaded: as INITAPP (which is special mode without GUI), when MicroStation starts, every time MicroStation opens a new design file etc.
- Based on the defined requirement, a proper configuration (probably using some variable like MS_DGNAPPS) can be investigated.
[quote user="Neil McGuire"]The addin should also be able to import models from a .dgn on disk into the open .dgn.[/quote]
To import a model from another deign file is a standard MicroStation feature. What is the reason to duplicate it?
With regards,
Jan