to enhance the code for tekla 

using System.Collections.Generic;
using Tekla.Structures.Geometry3d;
using Tekla.Structures.Model;
using Tekla.Structures.Model.UI;

namespace UserMacros
{
    public class CombineToContourPlate
    {
        public static void Run(Tekla.Macros.Runtime.IMacroRuntime runtime)
        {
            Model model = new Model();
            if (!model.GetConnectionStatus())
            {
                Tekla.Structures.Model.Operations.Operation.DisplayPrompt("Model not connected!");
                return;
            }

            // ✅ Use UI selector (avoid namespace conflict)
            var uiSelector = new Tekla.Structures.Model.UI.ModelObjectSelector();
            var selectedObjects = uiSelector.GetSelectedObjects();

            List<Point> contourPoints = new List<Point>();
            List<ModelObject> originals = new List<ModelObject>();

            while (selectedObjects.MoveNext())
            {
                ModelObject obj = selectedObjects.Current as ModelObject;

                if (obj is Beam)
                {
                    Beam beam = obj as Beam;
                    Point start = beam.StartPoint;
                    Point end = beam.EndPoint;

                    double thickness = 0.5;
                    beam.GetReportProperty("PROFILE.PLATE_THICKNESS", ref thickness);

                    contourPoints.Add(start);
                    contourPoints.Add(end);
                    contourPoints.Add(new Point(end.X, end.Y, end.Z - thickness));
                    contourPoints.Add(new Point(start.X, start.Y, start.Z - thickness));

                    originals.Add(beam);
                }
                else if (obj is ContourPlate)
                {
                    ContourPlate pl = obj as ContourPlate;
                    foreach (ContourPoint cp in pl.Contour.ContourPoints)
                    {
                        // ✅ Fix: use cp.GetCoordinate() instead of cp.Position
                        contourPoints.Add(cp.GetCoordinate());
                    }
                    originals.Add(pl);
                }
            }

            if (contourPoints.Count < 3)
            {
                Tekla.Structures.Model.Operations.Operation.DisplayPrompt("Select at least one valid plate or beam.");
                return;
            }

            ContourPlate newPlate = new ContourPlate();
            newPlate.Profile.ProfileString = "PL1";
            newPlate.Material.MaterialString = "A36";
            newPlate.Name = "CombinedPlate";
            newPlate.Class = "6";

            foreach (Point pt in contourPoints)
            {
                newPlate.AddContourPoint(new ContourPoint(pt, null));
            }

            if (newPlate.Insert())
            {
                Tekla.Structures.Model.Operations.Operation.DisplayPrompt("New combined contour plate created.");
            }
            else
            {
                Tekla.Structures.Model.Operations.Operation.DisplayPrompt("Failed to insert contour plate.");
                return;
            }

            // ✅ Correct yes/no dialog
            int response = Tekla.Structures.Model.Operations.Operation.DisplayYesNo("Delete original plates/beams?");
            if (response == Tekla.Structures.Model.Operations.Operation.DisplayYesNoEnum.Yes)
            {
                foreach (var obj in originals)
                {
                    obj.Delete();
                }
                Tekla.Structures.Model.Operations.Operation.DisplayPrompt("Original parts deleted.");
            }
            else
            {
                Tekla.Structures.Model.Operations.Operation.DisplayPrompt("Original parts kept.");
            }

            model.CommitChanges();
        }
    }
}



Comments

Post a Comment

Popular posts from this blog

actions events in itext 7

In iText 7, the @event annotations you might be seeing are not global variables. Instead, they are typically referring to event handlers related to document processing, such as handling page events, table events, and paragraph events. These events allow customization of how a document is generated. 🔹 Where Do These @event Appear in iText 7? In Java and C# (iText7 .NET), event handling in iText 7 is implemented using interfaces such as: 1. IEventHandler → The main event interface. 2. PdfDocumentEvent → Used to handle document-level events. 3. TableEvent → For handling table modifications. 4. ParagraphRenderer → For customizing paragraph rendering. These events are not global, but rather tied to specific elements in the document. --- 🔹 Example: Handling Page Events in iText 7 1️⃣ Implementing a Custom Page Event Handler In C# (iText 7 .NET), you can create a class that implements IEventHandler to modify the pages. using System; using iText.Kernel.Pdf; using iText.Kernel.Events; using i...
Read more

midi_sequence_playing_real_time

 Below is a simple C# program using NAudio to play a MIDI sequence in real-time using a Windows Forms application. Ensure you have the NAudio NuGet package installed in your project. Steps to Set Up: Open Visual Studio and create a Windows Forms App (.NET Framework) project. Install the NAudio package via NuGet: mathematica Install - Package NAudio Replace the Form1.cs content with the following code. Code csharp using System; using System.Windows.Forms; using NAudio.Midi; namespace MidiPlayerApp { public partial class Form1 : Form { private MidiOut midiOut; private Timer playTimer; private int currentNoteIndex = 0 ; private int [] midiNotes = { 60 , 62 , 64 , 65 , 67 , 69 , 71 , 72 }; // MIDI notes for C major scale private int duration = 500 ; // Duration for each note in milliseconds public Form1 () { InitializeComponent(); InitializeMidi(); } priv...
Read more

GTTERMS_FORMALIZATION_GEOMETRIFYING_TRIGONOMETRY

Introduction to Sanjoy Nath's Geometrifying Trigonometry Fundamental Philosophy: Sanjoy Nath's Geometrifying Trigonometry introduces a profound shift in the way we understand division and arithmetic operations. Traditionally, division is seen as a simple numerical operation. However, in this new paradigm, division is reconceptualized: the denominator is viewed as an input object, and the numerator as an output object. This shift represents a significant epistemological change in the reasoning processes of mathematics. Epistemological Shift: This new philosophy posits that any denominator, whether abstract or concrete, functions as an input object, while the numerator serves as the output object. Additionally, arithmetic operations are no longer seen as producing a single output. Instead, each operation can generate multiple outputs, including a primary output and secondary, or complementary, outputs. This reflects a natural phenomenon where processes that occur sequentially a...
Read more