[Bug] view.draw_points kills next draw instruction
-
I just noticed this:
After using
view.draw_points- the nextview.draw_*method except anotherview.draw_pointsis being ignored.
After the first following [ruby]view.draw_*[/ruby is ignored - everything works fine again. -
Ahh bummer, that is very odd. I have not used that method yet, though I was about to sometime this week. If I see anything different, I'll post it here.
Chris
-
Please do so.
I noticed before some draw calls where not recognized, but I never worked out why. I just happneed to see this correlationship.And I wonder if this is a new one. Maybe new to 7.1. I don't have SU7.0 or SU6 installed any more...
-
I think there is something wrong with the draw calls inside Sketchup. I've logged a bug with Google as if you do a glGetError() afterward it returns "over/underflowing matrix stack" like they've popped once too often.
-
@adamb said:
I think there is something wrong with the draw calls inside Sketchup. I've logged a bug with Google as if you do a glGetError() afterward it returns "over/underflowing matrix stack" like they've popped once too often.
I noticed that. Do you see it after calling
draw_points? -
I just noticed a similar "bug", but it occured when I supplied a nil value as a point3d to the draw_text method. So I thought I had recreated Thom's bug, but really it was just because I gave the method a non-existant instance variable.
Chris
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login
Advertisement