<wpwrak>
whitequark: by the way, that g002 with the not closed contour and its failed extrusion both showed as "ok" in the text window. might be a good place to show something red, even some other aspects of them are indeed "okay"
<whitequark>
wpwrak: but it already shows you red text over all the geometry
<whitequark>
that is unless you have turned that off...
<wpwrak>
grmbl. and the difficulty in bringing up my displaced TW is back :( so whatever is at the root of that problem isn't solved yet. just goes dormant at times. just the sort of bug i like best :(
<whitequark>
no luck with GDK_DEBUG=ALL ?
<wpwrak>
whitequark: yes, the red text is there, but only if you're in that group. so if you miss it there and go elsewhere, you won't notice so easily
<wpwrak>
not sure how i missed it in the first place, though. maybe some gremlin sneaked in and changed the "G" while i was sleeping :)
<whitequark>
mmh, I think the idea was that sketches with no closed contour aren't inherently broken, extrusions from them are
<wpwrak>
(GDK_DEBUG) yeah, that'll be next
<whitequark>
solver errors generally make the entire file unusable until they are fixed
<whitequark>
not-closed-contour, not so much, and the result is generally immediately obvious
<whitequark>
I was just wary of intermingling the "error: until you fix this you won't be able to get anything done" and "error: this maybe doesn't do what you want, or you forgot it in the middle of something" states
<travis-ci>
whitequark/solvespace#638 (master - 6c0e30f : whitequark): The build was fixed.
<wpwrak>
hmm, a "make install" without regression tests would be nice.
<wpwrak>
aaah ... i'm getting an idea of what is happening with the disappearing text window. could be that, if the window manger remember having it seen on a different virtual screen, it just sends it there. so it disappears on the current screen but isn't really lost
<wpwrak>
hmm. maybe. not sure if actually enough would work without a wm to get a meaningful test. but i can try it some time. it means taking down my entire session (with some 100 windows), though
<whitequark>
but it can be done with some judicious use of xwininfo+xdotool
<wpwrak>
;-))
<wpwrak>
gah. parameter tables would be SO useful. e.g., for this touch panel + OLED design: one set of parameters with the window just for the OLED, and one with the window for the panel. all the rest is identical.
<whitequark>
I totally agree
mumptai has joined #solvespace
<wpwrak>
hmm, i wonder if it's actually ever really useful that the active group doesn't automatically follow the selected group. that's a feature that's really hard to get used to.
<whitequark>
it absolutely is
<whitequark>
one case where I find it useful is when you want to select an entity or constraint from a previous group