That inspecting only works if the macro has reached that breakpoint and is halted.
You need to click OK in the macro window to start it. Since it doesn't have any code it should reach the line with the breakpoint quickly. Once you see the yellow arrow in the red breakpoint dot you should be able to inspect variables/objects.
On rare occasions I have seen that it doesn't work if you restructured your solution, i.e. moved a macro to a subfolder. Then it starts working again if you stop debugging, close VS, restart VS, load the solution and start debugging again.
I often add a line like
tt = 1
or similar to my code, i.e. in loops in order to set a breakpoint and inspect the content of variables before the next iteration.
Stepping through the code, as you might know it from VisualBasic, or Intellisense, or code completion all doesn't work with Ironpython. Debugging is very limited to setting breakpoints and inspect variables.
------------------------------
Ronny Schneider
------------------------------
Original Message:
Sent: 05-11-2022 06:40
From: john chronister
Subject: Issues settings up VS2019 and accessing Ironpython WPF Window
Last Question, I promise...
When you mouse hover over the object name and that menu shows up, mine doesn't do that? How are you able to do that?
------------------------------
john chronister
Original Message:
Sent: 05-10-2022 21:59
From: Ronny Schneider
Subject: Issues settings up VS2019 and accessing Ironpython WPF Window
You should nearly have everything you need.
In theory you should copy the ZIP-File from "C:\Program Files (x86)\Trimble\Macros SDK\Templates\2019" to
"C:\Users\your user path\Documents\Visual Studio 2019\Templates\ProjectTemplates".
The thing is that this template is rather old and won't really work with TBC 5.50 and above, the namespaces did change a bit. Better copy the attached one into the template folder. And once you've setup your solution you don't want to create a new solution for every single macro. You only create a new subfolder, copy and paste a previous macro into it and rename it. You only need this template once, at least I do it this way.
You don't have to re-start TBC after every code change, just close and re-start the macro.
Though, in order to interactively edit the UI in the XAML editor you need to stop debugging and close TBC. If you know exactly what you do and you don't need the graphic feedback of the XAML editor you can just edit the code and re-start the macro in TBC.
------------------------------
Ronny Schneider
Original Message:
Sent: 05-10-2022 14:17
From: john chronister
Subject: Issues settings up VS2019 and accessing Ironpython WPF Window
Trying to follow the library instructions on getting started with programming TML's, but my VS2019 absolutely does not want to cooperate with doing what the instructions are saying. I've installed the studio, installed ironpython and made sure it was checked in individual components, installed Trimble MacroSDK. First, my TBCMacro template doesn't show up under the python section of project creation, but I am able to get it when I search for it. Once I'm in the project, I am stuck at the instructions to "Add New Item..." because there is no ironpython WPF Window option, or anything ironpython in there at all. My environment is set to iron python, but I can't seem to get past this step.
------------------------------
john chronister
------------------------------