Topic for #qi-hardware is now Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs
wej has joined #qi-hardware
LunaVorax has quit [Remote host closed the connection]
<qi-bot>
[commit] Werner Almesberger: b2/: add relop to struct param, in preparation of merge with struct var (master) http://qi-hw.com/p/eda-tools/fdac542
<qi-bot>
[commit] Werner Almesberger: b2/: rename "name" field in struct value to more generic "s", for better sharing (master) http://qi-hw.com/p/eda-tools/061e8f5
<qi-bot>
[commit] Werner Almesberger: b2/: use (general) "struct param" to replace (specialized) "struct var" (master) http://qi-hw.com/p/eda-tools/c1b6b2a
<cladamw>
wpwrak, in GUI, how can I select 'marker' frame to add vector ? I found that in my *.fpd, those __0: vec @(-x/2-r-clear, -y/2+r)__1: vec .(0mm, r) is not within "marker' macro. And surely in GUI screen will get blue background. Of course I can 'manually' copy vectors into frame macro, but I'd like to do this in GUI. What else i can do ? or just use "Swap var&code" ?
jivs_ has joined #qi-hardware
<wpwrak>
cladamw: you just click on the name ("marker") in the list of frames. then what you do on the right side happens in the marker frame
<wpwrak>
cladamw: note: if you later click on an item that's in a different frame, fped may change the current frame to the one containing that item
<cladamw>
so select frame first, then add vector, etc ... at that those vectors would be included in 'marker' ?
<wpwrak>
when you add vectors, they're always added to the current frame
<cladamw>
hmm ... need to get used to .... seems the 'start' and 'end' point are hard to click. :(
<cladamw>
and period of clicking changes frame layer.
<wpwrak>
but you'll have to connect the "marker" frame first. so you select the frame in which it should be placed, then drag "frame" on the location where its origin should be (the origin is the fat little circle)
<wpwrak>
so the complete sequence for creating a new frame and then adding things to it is:
<wpwrak>
1) "Add frame" on the left side
<wpwrak>
2) edit the name of the new frame (default name "_")
<wpwrak>
3) select the parent frame
<wpwrak>
4) drag the new frame (click and hold the name, then drag it into the canvas) to its starting location
<wpwrak>
5) select the new frame (on the left side again)
<wpwrak>
6) so to the canvas and add the things you want there, starting from the frame's origin
<wpwrak>
note that a frame can have multiple parents. e.g., if you have a vector (10, 0) and a vector (-10, 0) in the root frame, you can attach "marker" (or some other frame) to each vectors
<cladamw>
ah ... seems 3) and 5) i missed or made wrong, alright, i try these 6 steps.
<wpwrak>
last but not least, the place where you attach a frame is the end of a vector in the parent frame or the parent frame's origin. so you don't have to make a vector (0, 0) to connect something to the origin
<wpwrak>
(3-5) yes, if you don't attach the frame, then the screen stays dark :)
<cladamw>
and why Fped generates many filename~#.fpd ?
<wpwrak>
these are older versions you've saved. that's to make sure that you have backups :)
<cladamw>
okay.
jekhor has joined #qi-hardware
cladamw has quit [Quit: Ex-Chat]
methril has quit [Ping timeout: 246 seconds]
xiangfu has quit [Ping timeout: 246 seconds]
methril has joined #qi-hardware
rejon_ has joined #qi-hardware
Martix has joined #qi-hardware
LunaVorax has joined #qi-hardware
<LunaVorax>
Hello everyone!
GNUtoo-desktop has quit [Quit: [INFO] fsogsmd : received signal -11, exiting.]
DocScrutinizer has quit [Disconnected by services]
<mth>
for me the distributed nature is not the major selling point of the new systems
<mth>
but that they treat a commit like the fundamental unit, rather than a tree state
<mth>
that's what makes merging in SVN so painful: you can only merge differences between two tree states onto a third tree, you cannot merge actual commits
<mth>
so you lose history when merging
<mth>
in practice, people have to keep a lot of administration outside of SVN to be able to merge between different branches
<viric>
it looks like you speak of darcs, and not of git
<viric>
in git, every 'commit' hash refers to a tree.
<mth>
darcs was the first system like that, but git takes more or less the same approach
<viric>
git manages trees
<viric>
it simply has many tricks to transform one tree to another
<viric>
(hence, changing commit hashes)
<viric>
- that's my view of git :)
<mth>
it changes commit hashes only for cherry-picking afaik
<mth>
if you merge, you create a merge node that has two parents
<viric>
any rebase too
<viric>
Commit Object
<viric>
The "commit" object links a physical state of a tree with a description of how we got there and why.
LunaVorax has quit [Remote host closed the connection]
jluis|work has quit [Ping timeout: 272 seconds]
jekhor has joined #qi-hardware
Ayla has quit [Ping timeout: 240 seconds]
GNUtoo-desktop has joined #qi-hardware
Ayla has joined #qi-hardware
Freemor has joined #qi-hardware
kilae has joined #qi-hardware
kristoffer has quit [Quit: Leaving]
djbclark has quit [Ping timeout: 250 seconds]
kristoffer has joined #qi-hardware
Ayla is now known as AwAyla
<qi-bot>
[commit] Werner Almesberger: b2/subst.c (prepare_re): fail on bad (#unit) syntax instead of ignoring (master) http://qi-hw.com/p/eda-tools/2946b83
<qi-bot>
[commit] Werner Almesberger: b2/subst.c (resolve_jump): use pointer comparison instead of strcmp (master) http://qi-hw.com/p/eda-tools/2ce2da5
<qi-bot>
[commit] Werner Almesberger: b2/: make "again" include the match; make "break" pop the stack (master) http://qi-hw.com/p/eda-tools/bb809b0
<qi-bot>
[commit] Werner Almesberger: b2/: make the match name after "break" and "continue" optional (master) http://qi-hw.com/p/eda-tools/694d48b
<qi-bot>
[commit] Werner Almesberger: b2/: for consistency, make "break/continue $" equivalent to "break/continue" (master) http://qi-hw.com/p/eda-tools/4f142c1
<qi-bot>
[commit] Werner Almesberger: b2/Makefile: generate dependencies also for YACC- and LEX-generated files (master) http://qi-hw.com/p/eda-tools/c9bd26a
<qi-bot>
[commit] Werner Almesberger: Makefile: generate dependencies also for YACC- and LEX-generated files (master) http://qi-hw.com/p/fped/6623ae1
antgreen has quit [Read error: Connection reset by peer]