| 07:38.02 | *** join/#qi-hardware infobot (ibot@rikers.org) |
| 07:38.02 | *** topic/#qi-hardware is Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben/atusb 802.15.4 wireless, anelok and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware |
| 07:38.02 | *** mode/#qi-hardware [+v infobot] by ChanServ |
| 09:23.12 | *** join/#qi-hardware jwhitmore (~jwhitmore@host81-148-226-110.range81-148.btcentralplus.com) |
| 10:39.56 | *** join/#qi-hardware arossdotme (~zxy@host-78-151-194-102.as13285.net) |
| 11:41.01 | *** join/#qi-hardware jwhitmore (~jwhitmore@host81-148-226-110.range81-148.btcentralplus.com) |
| 12:33.31 | *** join/#qi-hardware pcercuei (~pcercuei@185.13.202.243) |
| 14:43.17 | *** join/#qi-hardware arossdotme (~zxy@host-78-151-194-102.as13285.net) |
| 15:03.57 | *** join/#qi-hardware wildlander (~wild@unaffiliated/wildlander) |
| 15:20.19 | wpwrak | whitequark: about the constraint markers: what i meant is more about exploration, e.g., when trying to see what constraints you've put. example: a rectangular U-shape. let's call the sides A, B, C. you'd have a perpendicular constraint for (A, B) and for (B, C). |
| 15:23.49 | wpwrak | there will then be an inverted T indicating the constraints on A, B, and C. on B, it seems that you may have one or two inverted Ts. let's assume it's one. so when you hover over any of the Ts of A or C, also the one in B is highlighted. |
| 15:24.15 | wpwrak | but if you hover over the one on B, only A or C is highlighted, so you don't see that there is a second one. |
| 15:28.06 | wpwrak | so that's a little inconsistent. not sure if it matters in the greater scheme of things, though, since i don't know yet the overall workflow for doing things in solvespace |
| 15:30.51 | wpwrak | by the way, regarding variables: in fped, i found it very useful to have tables as means of iteration. each column represents a variable, and each row is an iteration step. so if i want three variants of the same structure, i make three rows and fill in the corresponding values. then fped iterates over the table and creates three different "instances". |
| 15:32.28 | wpwrak | and of course, every value can be an expression. and expressions are stored as expressions and only evaluated when anything has changed (i just rebuild the whole drawing each time any change has happened - modern computers are more than fast enough for this ;) |
| 17:09.23 | *** join/#qi-hardware sb0 (~lekernel@123202036228.ctinets.com) |
| 20:21.05 | *** join/#qi-hardware sandeepkr_ (~sandeep@111.235.64.4) |
| 20:24.53 | *** join/#qi-hardware sandeepkr_ (~sandeep@111.235.64.4) |
| 20:28.26 | *** join/#qi-hardware sandeepkr_ (~sandeep@111.235.64.4) |
| 20:30.42 | *** join/#qi-hardware sandeepkr_ (~sandeep@111.235.64.4) |
| 20:32.53 | *** join/#qi-hardware sandeepkr_ (~sandeep@111.235.64.4) |
| 21:49.29 | whitequark | wpwrak: yes, what you're suggesting is clearly very valuable, and it's been on my roadmap for months |
| 21:49.41 | whitequark | unfortunately, some serious refactoring needs to be done before that's implemented |
| 22:45.42 | wpwrak | refactoring, the joy of OO - at least you have a word for it ;-) |