Pat Stanford

I failed to notice this was for worksheet instead of for Vectorscript. I will have to look tomorrow if it will work in worksheet. Something similar should.

Look at C_HR and https://www.asciitable.com Capital A is C_HR(65), lower case a is C_HR(97) So C_HR(64+YourVariable) will give you the character in capital letters, C_HR(96+YourVariable) will give you the lower case. The forum does not allow the use of the real function name. So take the underscore out and it should work.

We will have to wait on Juan on this one. I see the same thing as you.

The Thumbs up from JuanP is probably the closest to an actual comment from VW on this. VW Employees are not allows to speculate on unannounced products. I as a volunteer can speculate all I want. But my statements above are based on being a close watcher of what VW does since 1991.

Worksheets not working on second monitor has already been reported as a bug. No way I know of to keep worksheet open for editing when you switch apps. Put a worksheet image on a layer and look at the image?

Yes, there seems to be a MacOS 14.4 (and 4.1) bug that is impacting programs on machines and is worse with machines with multiple monitors. Hopefully Apple will release 14.4.2 or 14.5 to fix this very soon.

Pure guess, but if the M4 is released before September, I am almost 100% certain VW2024 will run on it. VW is unlikely to not make sure VW2024 is running on the most current OS when VW2025 is released. If the M4 slips to late spring 2025 AND the OS changes required to make it work are substantial it is possible/probable that VW would not fix the older version to work with the newest OS. It depends on what Apple does with the next OS.

My reading of the question is that @SimA wants to define the chord length and then calculate where that chord length next contacts the polyline. So drawing the circle at the first point is relatively easy. And comparing even a few thousand lines to intersect the circle should not be too bad as it can be solved in linear time not exponential time since you don't need to compare every line to each other. And maybe add the bounding box check we discussed in the other thread so you don't have to actually test objects that dont' have any chance of being the chord. But a better description of what is actually being done and why might let us generate better options.

Mac OS 14.2 on a M3 chip.

You could go back to VW2023. Or MacOS 14.3. It appears to be an Apple problem. I am not certain why there has not been a 14.4.2 release to fix this. I believe that 14.5 is in Beta. 🤞

For me in VW2024U4 the P key on the Offset Tool does exactly what you asked for. And so does the enter key from the num pad (or the keyboard).

I know there is not a simple built in way to do this. But I am not certain how I would approach this if it was my problem. It is simple to get a visual representation of the intersection by drawing a circle from the first point with a radius equal to the chord length you want. The hard part is actually getting the intersection as none of the intersect routines in the Graphical Calculation section of the VS Function Reference appear to work with Polylines. Maybe convert a copy of the polyline to Lines, which should give you a group of lines. Then check each line for intersection with the circle? @Sam Jones We had a conversation 20 years ago about Chords. Any help here? And a call to the regular VS warriors @MullinRJ @JBenghiat @michaelk @Jesse Cogswell

I don't think you are going to be able to create your vision in a basic Vectorscript. I think you will need to go to an Event Enabled script that will give you far more control over how the object/tool interacts with the UI. I have never done Event Enabled, so I will not be much help there. @Jesse Cogswell has done several posts about Event Enabled including this one with an example script. I think he did another longer text description also, but I can't find it right now. Python (at least the VW implementation) does not have a good way to pause execution while waiting for operator input, so you might be better off keeping this object in Vectorscript to make using the UI commands simpler. Good Luck.

I have not used RunTempTool. Why does the command down need to be inside the loop? Why not end your object with a double click and then do the check for the keydown outside of the Callback? Have you seen this thread?