search

SketchUp / sketchup-ruby-debugger

Ruby API debugger for SketchUp 2014 and later.
MIT License
78 stars 34 forks source link

Close then open a new TCP connection? #7

Closed jimfoltz closed 7 years ago

jimfoltz commented 8 years ago

Should it be possible to close the socket connection to the debug server, then open a new connection?

Currently if I close the socket connection, I get the message system:10054 from SketchUp in my debugger window. The debug server does not respond when I attempt to open a new connection.

Attached is a screen-shot of a simple session.

NOTE - I have also seen the message asio.misc:2 when disconnecting but I'm not sure how to reproduce one result over the other.

2016-03_376

BugraBarin commented 8 years ago

Hi Jim, Currently the server will wait for a connection initially but won't listen for a new connection if the client disconnects. This would be a nice feature to implement.

jimfoltz commented 8 years ago

Thanks for the reply, @BugraB .

I ask this because I am starting to like vscode and the vscode/ruby extension for writing SketchUp extensions - vscode has nice git and debugger support, but vscode/ruby does not quite play well with the SketchUp debug server. I'd like to improve that.

BugraBarin commented 8 years ago

I really like vscode too and believe it or not I thought about this very thing the other day. I'd love to work on that but there are just too many projects and too little time in the day :-)

jimfoltz commented 7 years ago

Just wanted to say thanks @seraku24 for this update. I compiled it last evening using VS2015 Express and after having to make one small change was able successfully use this version in VSCode.

thomthom commented 7 years ago

@jimfoltz what was the change you had to do?

jimfoltz commented 7 years ago

It was adding the "public" keyword at RDIP.cpp line 34. I see it has already been added by @BugraB.

https://github.com/SketchUp/sketchup-ruby-debugger/blob/master/DebugServer/UI/RDIP/RDIP.cpp#L34