attached file is a design file for my task 103812.

huangyhg

Yanhua,



I reviewed your design. It looks good except to the new static DLL. Is there a reason why we need a new dll to create the FCF dialog? You will need to work with Porter on how the user will specify the location and leader line in the graphic display. Maybe have a “Placement” button that brings up a placement and leader line dialog.





Rick Tischler

Product Development Manager

PC-DMIS Inspection Planner

Wilcox Associates, Inc.

Phone/Fax (586) 226-2717

[email="Rick.Tischler@HexagonMetrology.com"]Rick.Tischler@HexagonMetrology.com[/email]



There are 10 types of people in this world.

Those who understand binary and those who don't.

From: Yanhua HUANG
Sent: Thursday, December 20, 2007 5:59 PM
To: Rick Tischler; Bill Velle
Cc: Don Turcotte; Paul Kitchen; Porter Bassett; Robert Jurca
Subject: attached file is a design file for my task 103812.




Rick,

Attached file is a latest design file for my task 103812 (Add ability for the user to create GD&T from the CAD model).



Yanhua Huang yanhua.huang@hexagonmetrology.com

huangyhg

Hi Yanhua (Yogy),

The GD&T callouts from Catia/Datakit/etc define the location of the FCF box, the orientation of the FCF box, and the fixed connection points to the cad surface, curve, etc. If desired, the user can drag the FCF to another location on the screen. There is special logic in Graphics to ensure that the leader lines are not drawn across the FCF box.



The GD&T callouts from PC-DMIS define the initial location of the FCF box and the bitmap image, along with the fixed connection points to the cad or features. Somewhere in the PC-DMIS GD&T engine there has to be logic to determine the fixed leader line end points (connection to the cad and features), along with the initial location of the FCF box. If desired, the user can drag the FCF to another location on the screen. There is special logic in Graphics to ensure that the leader lines are not drawn across the FCF box.



BV






From: Yanhua HUANG
Sent: Monday, December 24, 2007 5:39 AM
To: Rick Tischler; Bill Velle
Cc: Don Turcotte; Paul Kitchen; Porter Bassett; Robert Jurca
Subject: RE: attached file is a design file for my task 103812.




Rick,

I select static DLL type to encapsulate FCF dialog, because the dll will import/export some classes. I select a DLL to encapsulate FCF dialog, because it is easier to debug code relative to FCF dialog and I hope reuse these code for PC-DIMS in the future.

Main code relative to create IP command and tolerance CAD object will be put into IP exe.

Porter,

Could you mind telling me more details about GD&T display in Inspection Planner? In my opinion, GD&T display location is decided by mouse event. Its leader line is a part of GD&T CAD object.

Yanhua Huang yanhua.huang@hexagonmetrology.com

huangyhg

Hi Yanhua,

You may have already thought of this, but I’ll ask these questions anyway…

1. Will the PC-DMIS GD&T dialog look exactly like the new GD&T dialog in the Inspection Planner?

2. Is the PC-DMIS GD&T dialog completely defined in the PC-DMIS resources?



If the answer to both of these questions is YES, then your new GD&T DLL could try using the PC-DMIS dialog defined in the PC-DMIS resources.  I do this for most of the Graphics dialogs that the IP uses – instead of creating a new resource entry/dialog I just reference the one that PC-DMIS has.



For example, you can access a PC-DMIS resource from inside the IP by doing the following:

  CInspectionPlannerApp* pThisApp = (CInspectionPlannerApp*)AfxGetApp( );

  HINSTANCE pcdmisResourceInstanceHandle = pThisApp->getResourceID(CInspectionPlannerApp::ResourceEnumPCDMIS);

  CIPSetResource  pcdmisResource (pcdmisResourceInstanceHandle); // LoadString, etc.



The function CInspectionPlannerApp::getResourceID will return the HINSTANCE of the requested ID.  There are 3 resources available: PCDMIS, Strings, the resources for the IP application.  In this example, we want the HINSTANCE associated with PCDMIS - ResourceEnumPCDMIS.



The HINSTANCE (pcdmisResourceInstanceHandle) is then passed to the constructor of the class CIPSetResource.  This will do the various AFX calls so that future resource requests (e.g. LoadString) will access the desired resource DLL.  Once that object associated with CIPSetResource goes out of scope, the destructor will reset the active resource to the previous resource.



You would still have to write the code for handling the various pushbutton events, scroll lists, etc, but you could probably copy some of that processing directly from the original PC-DMIS events.



The positive side of using the same resource as PC-DMIS is that the resources are already translated to other languages, and the look of the dialog should be identical.



Your choice if you want to use the PC-DMIS resources – just thought I would mention it to you…

BV

huangyhg

Hi Yanhua,

Some of the Graphics Dialogs that the Inspection Planner uses from PC-DMIS are also a little different. I was fortunate that only a few buttons had to be hidden. There are two issues that you would have to address:

• Usually, labels are just defined as ID_STATIC (?), so there are no unique names. You would have to modify the PC-DMIS resources to assign a unique identifier to the labels so that when you used the dialog resource in your new DLL you would be able to find all of the labels that need to be hidden.
  
• Depending on the number of labels & buttons that need to be hidden, you might have to put in extra logic in your DLL to adjust the overall size of the dialog to eliminate large blank areas. Sometimes, this can be painful. This will probably determine if you want to use the PC-DMIS resources for the dialog.
  

It is your choice if you use the PC-DMIS resources or if you create a new dialog resource in the “IPRESOURCE”.

BV

From: Yanhua HUANG
Sent: Tuesday, December 25, 2007 6:54 AM
To: Bill Velle
Cc: Don Turcotte; Paul Kitchen; Porter Bassett; Robert Jurca; Rick Tischler
Subject: RE: attached file is a design file for my task 103812.




Merry Christmas!

Don,

Is the PC-DMIS GD&T dialog completely defined in the PC-DMIS resources? I found there is a special control or OCX in advanced page of GD&T dialog. Which role is the special control or OCX? Which parameters did you define in advanced dialog?

Need the advanced page display in Inspection Planner?

BV,

Thanks.

1. Will the PC-DMIS GD&T dialog look exactly like the new GD&T dialog in the Inspection Planner?

>Yes. But we plan to remove definition datum function from GD&T dialog.

Yanhua Huang yanhua.huang@hexagonmetrology.com

huangyhg

Yanhua,

The PC-DMIS GD&T dialog is completely defined in the PC-DMIS resources.  What special control or OCX are you referring to?



The advanced tab dialog supports output parameters including which axes are reported in the summary table for true position callouts.  In addition information on the type of fit to be used for “Form only” profile is supported on the Advanced tab.  It is not necessary to include the Advanced tab dialog in Inspection Planner since PC-DMIS will use default values for everything on the Advanced tab but it may be useful to allow the user to define these parameters in Inspection Planner rather than having to edit the PC-DMIS  program if the user wants values other than the defaults.



Regards,

Don

huangyhg

I would recommend creating a new dialog resource in IPRESOURCE.  Trying to use the same resources as PCDMIS has cost us a lot more time than it has saved overall.



Porter Bassett [email="porter.bassett@hexagonmetrology.com"]porter.bassett@hexagonmetrology.com[/email]