Ken Adams's Activities

Is the any API's or SDK for Cloud/Web services?

Ken Adams — Mon, 06 Mar 2023 19:08:13 GMT

Is there any way to programatically check to see if somebody has registered with Bentley?

For the time being we are still using MicroStation SS3 which does not require you to register. If I could check if a user was registered programatically I could required registration.

is there any way to do this?

Ask A Question II

Wed, 27 Jul 2022 12:51:14 GMT

Ask 10 questions in a forum.

Port SS3 MDL to CONNECT or rewrite in VBA

Ken Adams — Wed, 27 Jul 2022 12:51:12 GMT

I understand this will depend on the type of program, but in general for element placement and manipulation tools, is it better to port SS3 MDL code to CONNECT, or rewrite them with VBA. Is there any criteria I can use to inform me of what path to go down?

SS3 defintion SYNONYMID_WorkingUnitItems not defined in CONNECT

Ken Adams — Fri, 22 Apr 2022 20:25:56 GMT

I am converting SS3 code that modifies working units and grid units using mdlModelRef_setWorkingUnits and mdlParams_setActive. In CONNECT, ActiveParams::SetValue looks like it works in a similar way.

As a final step I am running mdlDialog_synonymsSynch(0,SYNONYMID_WorkingUnitItems,NULL ); to get the working units dialog to reflect the changes.

status = mdlModelRef_setWorkingUnits (modelRef, &newMasterUnits, &newSubUnits);

mdlParams_setActive((void *)gridref, ACTIVEPARAM_GRIDREF);
mdlParams_setActive(&gridunits, ACTIVEPARAM_GRIDUNITS);
mdlParams_setActive(&unitrndoff, ACTIVEPARAM_UNITROUNDOFF);

mdlDialog_synonymsSynch(0,SYNONYMID_WorkingUnitItems,NULL );

In SS3 in dlogids.h, SYNONYMID_WorkingUnitItems is defined as: #define SYNONYMID_WorkingUnitItems (BASEID_WorkingUnits-1)

SYNONYMID_WorkingUnitItems is not defined in CONNECT.

Is there a way to sync up the working unit dialog? Maybe it is not necessary anymore? I have not finished porting the code so I can't verify how it works yet.

I am inclined to just comment out that mdlDialog_synonymsSynch line for now and revisit it after my application is up and running.

TextEDParam compile error in CONNECT works in SS3

Ken Adams — Fri, 15 Apr 2022 18:54:28 GMT

I have a function in SS3 that accepts a pointer to a TextEDParam structure.

In CONNECT, I added the include file

#include <DgnPlatform\TextParam.h>

This include file looks like it defines TextEDParam. (in SS3 it was defined in mdl.h)

Yet for this function:

Public nativeCode void fplcom_justTxtToEditField(TextEDParam *edParam);

I am getting this compiler error: error C2065: 'TextEDParam': undeclared identifier

Any idea what is going wrong here?

How to compile CONNECT examples in Visual Studio 2019

Ken Adams — Thu, 14 Apr 2022 20:56:08 GMT

I can compile all examples in the CONNECT SDK in the developer shell. Now I am trying to open the solutions in Visual Studio 2019 and compile inside VS.

I made a copy of MicroStationDeveloperShell.bat and added this line at the end so Visual Studio would open:

"C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\devenv.exe"

When I open MyApp.sln and try to compile, I get this output:

Rebuild All started: Project: MyApp, Configuration: Debug Win32 ------
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VC\v160\Microsoft.MakeFile.Targets(50,5): warning MSB8005: The property 'NMakeReBuildCommandLine' doesn't exist. Skipping...
1>Done building project "MyApp.vcxproj".
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========

I know in SS3, had to create a solution and manually add the build Command Line in the NMake property.

Since the CONNECT examples already have solution files, I assumed this would not be necessary. Am I missing something?

As a test, manually added the build Command Line and added the mdl\include path in hte Include Directors.

But this only got me so far. It is producing the mdlapps.ma file but not mdlapps.dll and I am getting many compile errors.

Is there any example of a shared library (.dll)? No .ma file.

Ken Adams — Tue, 12 Apr 2022 16:01:16 GMT

I have a shared library (stand alone .dll file. No .ma file.) Is there any example of this in the CONNECT SDK?

compile error trying to convert MDL to CONNECT

Ken Adams — Mon, 04 Apr 2022 19:52:07 GMT

I installed VS2019, CONNECT and its SDK and I can compile the examples without a problem..

I am trying convert an MDL from SS3 to CONNECT. It is already in .DLL form and compiles within VS in SS3.

When the compiler gets to the type resource, I get this error:

[== Building D:\Users\KWA0GSU\AppData\Local\Temp\Bentley\MicroStationSDK\objects\fplcmd.rsc, (D:\fpl\devStudio\fplmdl\src\fplcmd.r) ==]
rcomp @D:\Users\KWA0GSU\AppData\Local\Temp\Bentley\MicroStationSDK\objects\make.opt
MicroStation Resource Compiler 10.16.01
BMAKE: no rules to build D:\Users\KWA0GSU\AppData\Local\Temp\Bentley\MicroStationSDK\objects\fpltyp.r
BMAKE: call trace
line: 69, D:\fpl\devStudio\fplmdl\src\fplmdl.mke
Mon Apr 04 15:30:20 2022, elapsed time: 0:00

My make file looks virtually identical to the myapp.mke example that compiles without error. Does anybody have any idea what could be going wrong here?

#------------------------------------------------------------------------
# Generate command table include & resource file using rcomp
#------------------------------------------------------------------------
$(o)fplcmd.h : $(baseDir)fplcmd.r

$(o)fplcmd.rsc : $(baseDir)fplcmd.r

#------------------------------------------------------------------------
# Create & compile the app's type resource using rsctype & rcomp
#------------------------------------------------------------------------
$(o)fpltyp.r : $(baseDir)$fpltyp.mt \
$(privateInc)fplids.h

$(o)fpltyp.rsc : $(o)fpltyp.r

#------------------------------------------------
# Set up to use dlmcomp.mki and dlmlink.mki
#------------------------------------------------

How to compile example mdl programs

Ken Adams — Wed, 27 Feb 2019 18:19:41 GMT

I have installed the latest Microstation Connect and SDK and am trying to compile some of the examples. Can anybody help me get this setup correctly?

mdlModelRefList_getCount gives unexpected results

Ken Adams — Fri, 09 Feb 2018 15:15:03 GMT

I am working with Microstation SS3 and using this code:

fObjP = mdlDgnFileObj_getMasterFile();
refListP = mdlDgnFileObj_getModelRefList(fObjP);
modelCnt = mdlModelRefList_getCount(refListP);

The results of this always return either 1 or 2. Some files that have 4 models (as shown in the Models dialog in Microstation) only return 2. Some files that have only 1 model return 2. Most files return 1 and correctly match what the Models dialog shows. But I am getting a mismatch for around 10% of my sample files.

Is the mismatch a sign of file corruption? Or is there something I am not understanding about how this function works?

Ask A Question I

Fri, 09 Feb 2018 09:33:17 GMT

Ask a question in a forum.

what is the best way to delete everything in a file except visible elements in view 1.

Ken Adams — Tue, 27 Jun 2017 13:46:23 GMT

I am looking to remove everything in a dgn file except what is visible in view 1. It looks like mdlScanCriteria_setViewTest will scan what I want to keep.And then I suppose I could create a new file with the mdlWorkDgn functions. But in years past that has not been the most reliable technique for me if the drawing has had any corruption in it.

What I would prefer is something that would scan what I want to delete. Or is there a better way to accomplish this?

BTW, I am on Microstation SS3.

MDL and upgrading MicroStation from SS3 to SS4

Ken Adams — Tue, 25 Apr 2017 18:12:55 GMT

I have a large body of MDL code last compiled and tested in SS3. It is still in pseudocode form. Do I need to recompile in order to upgrade MicroStation from SS3 to SS4? Do I need to convert to nativecode? Can you direct me to any FAQs about making this port? Thanks for any info you can provide.