2016-05-08 00:02 wpwrak: pushed 2016-05-08 00:02 also now clean wrt -Wall -Wextra, at least over here 2016-05-08 00:03 ah, just did the full build :) let's see ... 2016-05-08 00:05 i don't see a push ? it's here, right ? https://github.com/solvespace/solvespace.git 2016-05-08 00:05 nono, whitequark/solvespace 2016-05-08 00:05 nightlies are still there 2016-05-08 00:05 since i force-push a lot and doing this to the main repo is hostile 2016-05-08 00:06 you should unlearn that force-push pattern :) 2016-05-08 00:06 no 2016-05-08 00:06 this is very deliberate 2016-05-08 00:07 i want history to be clean, and i don't want to build everything on three systems manually 2016-05-08 00:07 btw, here are the warnings i got before. just two more: https://neo900.org/stuff/paste/Aegee5qu 2016-05-08 00:07 so if something comes up on the OS X buildbot? I fix it and force-push 2016-05-08 00:07 git submodule update too 2016-05-08 00:10 i guess yuo could just use a push-to-build-test repo. then fix things locally before pushing to the public repo. 2016-05-08 00:12 let's see how the new build goes ... 2016-05-08 00:12 i also edit history when i forget something 2016-05-08 00:12 which is like every other commit 2016-05-08 00:12 and no, "forget less" is not an option. so deal with it, i guess, or never use the nightly repo 2016-05-08 00:12 sure. rebase -i is fun :) 2016-05-08 00:12 i mean edit published (to whitequark/solvespace) history 2016-05-08 00:13 rebase -i locally is harmless 2016-05-08 00:13 exactly. that's what i mean: i also often forget something when committing, so i let things rest for a bit before pushing 2016-05-08 00:14 build it noticeably cleaner now :) just the auto_ptr complaint left now 2016-05-08 00:15 yeah. can't do anything about that. 2016-05-08 00:15 btw, my ubuntu didn't like the libgtkmm-2.4-dev libpangomm-1.4-dev dependency. had to use aptitude to find a solution at all, and it involved downgrades. but i'm not sure if this isn't a result of having a slightly odd setup here (accidently upgraded once into a testing release, and haven't been able to completely shake off the consequences yet) 2016-05-08 00:17 what did you use before? 2016-05-08 00:18 back to raising ... seems that a gtk dialog doesn't have to make the main window raise. so there's another quirk somewhere in solvespace. 2016-05-08 00:19 i think it was some 14.xx, then jumped to xenial a few months ago. so far the installer hasn't recognized my right to upgrade to release 16.04 2016-05-08 00:20 no, which *mm-dev packages 2016-05-08 00:20 or what did they cause to downgrade 2016-05-08 00:20 lemme see if it's still in the scroll buffer ... 2016-05-08 00:22 this is the negotiation with aptitude: https://neo900.org/stuff/paste/ra6Ver5e 2016-05-08 00:24 to test the window raising on dialogs, you can use fped: just run fped, put something over its window, then select File > Save as. the dialog pops up, on top, but the main window stays at its original position 2016-05-08 00:24 the same experiment with solvespace makes GW jump to the front as well 2016-05-08 00:27 re -dev packages: no idea. the dependency looks right to me. no clue why apt wants to downgrade 2016-05-08 00:32 wpwrak: regarding dialogs, you set parent window to NULL in fped 2016-05-08 00:32 and I set it to *GW 2016-05-08 00:33 i'm not going to change that because your behavior is, in fact, incorrect 2016-05-08 00:34 (specifically, a dialog should be a modal window placed where the graphics window is) 2016-05-08 01:31 doomlord_ has joined #qi-hardware 2016-05-08 01:35 arossdotme-planb has quit [Quit: Ex-Chat] 2016-05-08 01:43 limpkin has quit [Ping timeout: 250 seconds] 2016-05-08 01:43 incomprehensibly has quit [Read error: Connection reset by peer] 2016-05-08 01:45 incomprehensibly has joined #qi-hardware 2016-05-08 01:46 limpkin has joined #qi-hardware 2016-05-08 02:11 (parent) ah, interesting. quirky stuff :) 2016-05-08 02:36 doomlord_ has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 2016-05-08 02:38 doomlord_ has joined #qi-hardware 2016-05-08 03:59 DocScrutinizer05 has quit [Disconnected by services] 2016-05-08 03:59 DocScrutinizer05 has joined #qi-hardware 2016-05-08 05:09 wildlander has joined #qi-hardware 2016-05-08 05:18 sandeepkr__ has quit [Ping timeout: 260 seconds] 2016-05-08 05:38 sandeepkr__ has joined #qi-hardware 2016-05-08 06:54 wildlander has quit [Quit: Saliendo] 2016-05-08 06:59 wildlander has joined #qi-hardware 2016-05-08 07:38 infobot has joined #qi-hardware 2016-05-08 09:23 jwhitmore has joined #qi-hardware 2016-05-08 09:47 jwhitmore has quit [Ping timeout: 265 seconds] 2016-05-08 10:25 arossdotme has quit [Ping timeout: 246 seconds] 2016-05-08 10:39 arossdotme has joined #qi-hardware 2016-05-08 10:42 sb0 has quit [Quit: Leaving] 2016-05-08 10:44 wildlander has quit [Quit: Saliendo] 2016-05-08 11:41 jwhitmore has joined #qi-hardware 2016-05-08 12:33 pcercuei has joined #qi-hardware 2016-05-08 13:30 arossdotme has quit [Ping timeout: 276 seconds] 2016-05-08 14:43 arossdotme has joined #qi-hardware 2016-05-08 15:03 wildlander has joined #qi-hardware 2016-05-08 15:20 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). 2016-05-08 15:23 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. 2016-05-08 15:24 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. 2016-05-08 15:28 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 2016-05-08 15:30 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". 2016-05-08 15:32 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 ;) 2016-05-08 17:09 sb0 has joined #qi-hardware 2016-05-08 18:07 wildlander has quit [Quit: Saliendo] 2016-05-08 20:21 sandeepkr_ has joined #qi-hardware 2016-05-08 20:24 sandeepkr_ has quit [Max SendQ exceeded] 2016-05-08 20:24 sandeepkr__ has quit [Ping timeout: 276 seconds] 2016-05-08 20:24 sandeepkr_ has joined #qi-hardware 2016-05-08 20:27 sandeepkr_ has quit [Max SendQ exceeded] 2016-05-08 20:28 sandeepkr_ has joined #qi-hardware 2016-05-08 20:30 sandeepkr_ has quit [Max SendQ exceeded] 2016-05-08 20:30 sandeepkr_ has joined #qi-hardware 2016-05-08 20:32 sandeepkr_ has quit [Max SendQ exceeded] 2016-05-08 20:32 sandeepkr_ has joined #qi-hardware 2016-05-08 20:33 sandeepkr_ has quit [Read error: Connection reset by peer] 2016-05-08 21:23 pcercuei has quit [Quit: dodo] 2016-05-08 21:49 wpwrak: yes, what you're suggesting is clearly very valuable, and it's been on my roadmap for months 2016-05-08 21:49 unfortunately, some serious refactoring needs to be done before that's implemented 2016-05-08 22:31 doomlord_ has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 2016-05-08 22:45 refactoring, the joy of OO - at least you have a word for it ;-)