rickm
Contributor
Joined 13 years ago
User Profile
User Widgets
Contributions
Re: Searching for the mapped object "btnYes" took a long time
Thank you so much for your interest and patience! I guess it's a complement to TC that I've gotten by for 13 years without ever having to look at this part of the system. Instead of 1000 words, here are some screenshots. btnCancel (and others) appears in both Mapped Objects and Aliases under the dlgSTRIPLOGError object, and it executes quickly. However, btnYes, btnNo and btnOK are under the main process (which is actually StripLog, not MyApp) in Mapped Objects but under dlgSTRIPLOGError in the Aliases. The context menu item "Find Mapped Object" in the Aliases section finds btnYes easily in the Mapped Objects section under the main process. It seems the mapping info is known, but not easily found at runtime. It's not clear to me what needs to be changed, and where to do it.Syntax.CreateInvoke no longer creates "Run Script Routine" for Keyword Test
I have a number of Script Extensions that I wrote over 7 years ago. Sometime in the last year or so the record actions no longer work properly, in that the syntax that is created no longer uses "Run Script Routine" and instead tries to invoke my function directly. Here is a sample of my code: // Generate the set code function CreateSetSyntax(ldName, name, value) { // Generate the treeHelp set call by calling the layoutDesignerSetValue script var call; call = Syntax.CreateInvoke(); call.ClassValue = "LayoutDesignerFunctions"; call.InvokeName = "layoutDesignerSetValue"; call.IsProperty = false; call.AddParameter(ldName); call.AddParameter(name); call.AddParameter(value); return call; } ... // Generate code for the set method var syntax = CreateSetSyntax(ldName, name, value); ... // Insert the generated code into the recorded script Recorder.AddSyntaxToScript(syntax); // Or: Recorder.AddTextToScript(Syntax.GenerateSource(syntax)); Both Recorder.AddSyntaxToScript() and Recorder.AddTextToScript() seem to do the same thing so I've used the first form all these years. Until recently the above inserted the following into my Keyword Test at record time: Run Script Routine LayoutDesignerFunctions - layoutDesignerSetValue "Aliases.StripLog.LayoutForm", "Track=Curve Track 1|Layer=Eng. Data|Property=Constrain to Grid", "False" but now it creates: LayoutDesignerFunctions layoutDesignerSetValue "Aliases.StripLog.LayoutForm", "Track=Curve Track 1|Layer=Eng. Data|Property=Constrain to Grid", "False" I don't mind changing my code if necessary, but I can't find how to fix this. Or did it get broken when they resurrected record-time script extensions awhile ago?Re: Indicator causing test to stop since 12.4 update but won't hide
I don't know if Jenny installed the same patch that I have. Mine is for 12.40, hers is for 12.41. My patch has replacement files for \Bin\tcCore.dll and \x64\Bin\tcCore.dll. I'm running 64-bit. The patch that I installed fixed two problems: Indicator.Hide() now works (from Run Code Snippet), and the Indicator no longer gets included in playback Region Checkpoints. In 6 years I've never had to hide the Indicator. I only tried to hide it and discovered that I couldn't a few days ago when I was desperate for a work-around to the Region Checkpoint problem. Without hiding it, just now I did a test where I sized and positioned a window such that the Indicator would cover some menubar items during playback. I recorded a test where I clicked those menu items and during playback the Indicator seemed to be hidden automatically during the mouse clicks and then appeared again afterwards. tristaanogre- I'd be interested to know when and why one would ever have to hide the Indicator?
