Bill C

That colon (:) notation business is what we have used for the New Window function. I don't know why it would be showing if you're not using that command.

The Save As Template for Catalog command was created to allow users to create Drawing Title Block catalog items. Like the ones in the ANSI Templates and ISO Templates catalogs. This command is different from the normal Save As because it only saves drawing elements that are assigned to a Layer with the Template option ON. Note that by default, when images are dropped onto a drawing they are put under a Group and the Group element does not have a Layer assignment. We group the image to more easily resize it. After the image is resized, you can UnGroup it and assign the image directly to the Logo layer (which by default has the Template option ON). To add an ICD to the Catalog, you use the Object command in the Right Mouse popup menu in a catalog. Select "Create from File". Then Browse to the ICD that was saved using the Save as Template for Catalog command. A3-logo.icd

My testing with IC2023SP1 shows that there is different behavior in ICD and EXB. Both are wrong but to different degree, therefore I will file separate QAs for the errors in ICD and EXB. For EXB it seems that the Through Hole setting from IronCAD Custom Holes and IC Mechanical Custom Holes is not being recognized for simple holes. Also not recognized for IronCAD Custom Hole for the counter-bore case. For ICD, it seems that the Through Hole setting is not being recognized for all simple holes regardless of whether they are from the Custom Hole Tool, IC Mechanical, or IronCAD Tools.

The reason we have provided the user with an option for both a "User" and "Group" file is to allow the case where a User might have some custom properties that are different from that of the larger organization (Group). For example, the Company might have specific custom properties that all it's users should use, like: COMPANY_NAME and this custom property would be stored in a common file in the intra-net. But each user will have his own file for his user-specific custom properties like DESIGNER_NAME, which will be stored in a user specific file. In the event that the same custom property is defined in both files, the User defined value wins.

Also, please note that questions related the IRONCAD's application programming interface (API) can be sent directly to apisupport@ironcad.com. That is really the fastest way to get an answer. thank you.

I am not sure what you mean by "rules". We have a Application Programming Interface (API). If you want to pass data between an external program (like a database) and IRONCAD, then you would need to write a program to do the work. The IRONCAD API supports C++ and C# programming languages. The description of the API is in the CHM files installed under C:\Program Files\IronCAD\2023\ICAPI\Docs\

The BOM in this drawing is associated with the view T.F.R. Because a layout view can have very many specific settings such as: Configuration and Display List, that control what is visible in the layout view ,the contents of a BOM that is associated with a view is really only valid for that view. Therefore, we should not allow users to create Item Bubbles on views that are not the view that is associated with that BOM. The bug is that we allow user to create the item bubble in the first place. But on the view update, we determine that the only BOM in the drawing is associated to a different view and so the Item Bubble is removed (because it is invalid). In a simple example with only one drawing and one BOM, this rule may seem excessive. But we have users that regularly create drawings with 50 sheets, and also must each sheet has a BOM, some sheets have no views and only a BOM for the entire drawing. In some cases they want item bubbles placed on a view for a BOM that is on a different sheet. And of course, users can add sheets and boms and views and remove them at different times. For this reason, it is necessary to have rules. In your case, you should create a BOM that is not associated with any view and not tied to a specific configuration. That way you can item bubble any view.

A hotfix has been created for this issue. The hotfix is for 2022 PU1 SP1.

Can you please provide a drawing that has this issue? thanks

The Description field is just a note the user can add to describe the style and does not have any functional purpose beyond what you see there.

It is not safe to use the same ID. There is a single sheetmetal table manager. The table id should be unique within the table manager, even though there are two types of tables (stock and tool). The table id is explicitly tied to the type of sheet metal tool (form or punch). When a sheet metal form or punch needs to get the parameters related to it's type (Lance, Double Lance, Louver, Keyway In, etc.) it will request the information from the manager using the Tool Table ID that it was assigned at creation. The manager will give it the first table it finds with that ID. Depending on sequence in which that table was added to the manager, it may or may not be the table you expect. Safer to just keep the Table ID unique.

Hello KKEKURS, Looking at your video, I noticed that sometimes the white edit control shows a comma decimal separator and sometimes it shows a period. Can you confirm that when the white edit control shows a comma decimal separator, the behavior is correct. And incorrect behavior when showing a period? Also, is your OS a Latvian OS? or is it English OS with Latvian Regional settings (minus the change you made to decimal separator)?

The image above indicates that there is a discrepency between what is being drawn by our UI (e.g., the 150,000 in light blue) and what the edit control uses for decimal separator (e.g. 150.000 shown in the white edit control) What happens with the other parts of our UI in this case? What about our SizeBox property page? What about Property Browser? What about Parameter table?

The Revision property was stored as an Integer, but the code that is trying to read it (when using the Menu-File-Properties command) only handles Strings. These document properties can also be read/edited from the Properties dialog, Custom page of the file. In that UI, there is an option about what type of data is being added: Text, Date, Number, Yes or No

Using the GLASS PIcket TYP.icd that you provided, I exported PDF with and without the embedded font Tools Option on resulting in the attached PDF files. Do you see the squares when you open these PDF files? Glass Picket TYP..pdf Glass Picket TYP.2.pdf

You can also elect not to project different types of elements vie the Edit Orientation dialog.

good to hear you are sorted out! In answer to an earlier question, I would recommend C# over VB.NET, simply because it is a "newer" language.

Are you asking if it is possible to have the string "IC -Assembly" added to the drop down list that appears in this dialog? Or do you simply want to be able to link the contents of the Page Text to a Custom Property on the Part or Document?

thank you. I was able to reproduce (actually in IC2018).

Could you please elaborate on #3 above? What exactly are your steps. Video?

Please check your scene file. Do you have any lights?

This can be done via the ICAPI. For example, you may have notice that the catalogs that come with the IC COMPOSE product include catalog items that launch the URL in the default web browser. These How To catalog items were created using ICAPI.

It has been proposed that we use colors, perhaps applied to the handles, to distinguish between the "right" or "left" side of the bend, or the "above" or "below" width? We would use similar color coding to tie the region of the sheet metal feature with the specific property being controlled by a property in the property page. Does that seem reasonable?

We tested some computers (Windows 10) in this office as well as a Windows 7 and all of them would load the ICS file that is double clicked into the running instance of IRONCAD. We also did some testing with the IronCAD Mechanical Utility. But since we did not have a case where double clicking always starts a new instance of IRONCAD, that was not very informative. However, I did find a similar complaint in the solidworks forum. I've attached the writer's comments below. So, for those users having a problem, I would check your HKCU\Software\Microsoft\Windows\CurrenVersion\Explorer\FileExts\.ics\UserChoice key. the ProgId value should be "IronCAD.Scene" If it is Application/ironcad.exe that is probably your problem. I was finally able to locate a Windows 7 machine which opens ICS files to a new ICCompose instance on double click and verified that the ProgId value was "Application/Iccompose.exe" I changed it simply using the Default Program console in the control panel.

It is not the length of the file name. It is the .2u at the end. The system thinks that you want the .2u as the file extension which doesn't fit with the expected .pdf extension so it just fails. You can get around it by simply putting in the .pdf after the desired file name. SG_MK5_LTHV2.2u.pdf The same problem occurs with other file types (ie., dwg or jpg) Admittedly this is not a friendly behavior. System should just take the file name as given, and add the .pdf as an extension. Just some poor logic in the implementation.