[Bug] view.draw_points kills next draw instruction

thomthom · 24 Feb 2010, 18:03

I just noticed this:

After using view.draw_points - the next view.draw_* method except another view.draw_points is being ignored.
After the first following [ruby]view.draw_*[/ruby is ignored - everything works fine again.

Chris Fullmer · 24 Feb 2010, 18:35

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

thomthom · 24 Feb 2010, 18:38

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...

AdamB · 24 Feb 2010, 20:50

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.

thomthom · 24 Feb 2010, 20:58

@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?

Chris Fullmer · 3 Mar 2010, 06:50

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