EditPythonScript broken?


(Brian Gillespie) #1

@stevebaer and @Alain

I’m feeling tremendously stupid, because I can’t get EditPythonScript to work.

I did the following in the daily build of Trunk V6

  1. Run EditPythonScript

  2. Type this script:

    import Rhino
    d = Rhino.RhinoDoc.ActiveDoc
    for object in d.Objects:
    pass

I put a break point in the “pass” line.

Then I clicked the green Play button.

the EditPythonScript window disappeared

I brought it back up, and couldn’t tell what was going on. I couldn’t tell if the debugger was stopped on a breakpoint, or if it was done debugging. I couldn’t edit the text, so I assumed it was debugging.

I then clicked Stop. Nothing seemed to change.

Then I closed EditPythonScript by clicking the red X. Rhino asked if I wanted to stop debugging; I clicked Yes, and the window stayed open. I closed it again.

Opening EditPythonScript, I still can’t edit the script.

What’s going on?


(Brian Gillespie) #2

Feeling much less stupid; this works great in V5 Trunk.


(Brian Gillespie) #3

This is http://mcneel.myjetbrains.com/youtrack/issue/RH-27314


(Steve Baer) #4

It’s still a pretty stupid script :wink: @alain, can you take a look at this?


(Brian Gillespie) #5

Yeah, the script got a lot less stupid after I was able to successfully use the debugger to discover what document and object functions I wanted to call! Unfortunately, V6 left me dead in the water, so I did allmy work in V5. —
Brian Gillespie


(Alain Cormier) #6

Hi @brian and @stevebaer,

My bad … sorry. It should be ok now. Youtrack has the details,

Cheers,
Alain