10:23 <GitHub> [solvespace] Leichtbier opened issue #173: select underlying line segement https://github.com/solvespace/solvespace/issues/173

16:47 <GitHub> [solvespace] wpwrak opened issue #174: distances can be hard to drag https://github.com/solvespace/solvespace/issues/174

16:57 <GitHub> [solvespace] wpwrak commented on issue #173: Now that we can select such things from the text window, perhaps a selection of multiple items could could make the items in question also selectable in the text window, with the option of de-selecting ? That way, an ambiguous selection could just select everything applicable, and the user could get rid of the undesired bits.... https://github.com/solvespace/solvespace/issues/173#issuecomment-2758596

18:50 <GitHub> [solvespace] whitequark commented on issue #173: We even should already have the list of entities under cursor. https://github.com/solvespace/solvespace/issues/173#issuecomment-275866656

18:53 <GitHub> [solvespace] whitequark commented on issue #174: @wpwrak do you have any sketch where this is reproducible? Please also post a screenshot with position/zoom settings that reproduce the issue. https://github.com/solvespace/solvespace/issues/174#issuecomment-275866840

19:15 <GitHub> [solvespace] wpwrak commented on issue #174: Here is one:... https://github.com/solvespace/solvespace/issues/174#issuecomment-275868148

19:17 <GitHub> [solvespace] whitequark commented on issue #174: confirmed https://github.com/solvespace/solvespace/issues/174#issuecomment-275868238

19:36 <wpwrak> hmm, if i have a design that has "naked edges" when forcing NURBS to mesh, but is fine if i turn that off, is this a bug or expected behaviour ?

19:42 <whitequark> amazing, never seen that

19:42 <whitequark> and yes a bug

20:05 <GitHub> [solvespace] wpwrak opened issue #175: forcing NURBS to mesh causes "naked edges" https://github.com/solvespace/solvespace/issues/175