search

buixuanan / fritzing

Automatically exported from code.google.com/p/fritzing
0 stars 0 forks source link

Silkscreen on bottom side of board for pin header (can not be moved to other side) #2839

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
See attached fzz, the headers J4 and J5 have their silkscreen somehow on the 
bottom of the board, as if the header has been moved to the other side - but as 
far as I can see there is no way to do that.

I have no idea how I managed it, but there you go, seems no way to move it back 
either.

Original issue reported on code.google.com by bitsybof...@gmail.com on 23 Dec 2013 at 12:16

Attachments:

GoogleCodeExporter commented 9 years ago 
Sorry for the belated response. I would not call this a bug. J4 is a 
through-hole pin header, and you can place these on either the top or the 
bottom. The reason you can't move J4 to the other side is because it is 
currently connected to SMD parts on the bottom layer; moving it to the top 
would break the connections. If you break the connections to the SMDs yourself, 
you can move it back to the top. J5 is a similar case.

Original comment by irasc...@gmail.com on 18 Jan 2014 at 12:58

GoogleCodeExporter commented 9 years ago 
The top/bottom drop down should grey out in this case, though.

Original comment by irasc...@gmail.com on 18 Jan 2014 at 1:01

GoogleCodeExporter commented 9 years ago 
As  a header has pads for every pin on both sides... shouldn't it be switchable 
even with smd components connected to it?  They would just reconnect to the 
corresponding pad from the other side.

Original comment by bitsybof...@gmail.com on 18 Jan 2014 at 10:10

GoogleCodeExporter commented 9 years ago 
Yes, you are right, you would have to flip the part over and reconnect the 
trace to the other side.

Original comment by irasc...@gmail.com on 18 Jan 2014 at 10:18

GoogleCodeExporter commented 9 years ago 
How exactly do you move a header to the other side, even without any traces 
connected to it?

There is no option to do so in the context menu, and the pcb layer drop-down in 
the inspector is not present for headers.

Original comment by bitsybof...@gmail.com on 18 Jan 2014 at 10:34

Attachments:

GoogleCodeExporter commented 9 years ago 
I used the pcb layer drop-down in the Inspector. I am not sure why it isn't 
visible in your version of Fritzing.

Original comment by irasc...@gmail.com on 18 Jan 2014 at 11:08

GoogleCodeExporter commented 9 years ago 
Recompiled from current git source today 
(bfde1caa2e1cefd8a3d960e8a91d0dfe76a27b9e), problem still remains, the drop 
down is not present in the inspector when a header is selected (even with no 
traces), as in the image above.

Original comment by bitsybof...@gmail.com on 18 Jan 2014 at 11:41

GoogleCodeExporter commented 9 years ago 
What platform are you on, and is the set up trivial, or do you want to upload a 
sketch file?

Original comment by irasc...@gmail.com on 19 Jan 2014 at 3:48

GoogleCodeExporter commented 9 years ago 
fzz attached for what it's worth (just a header on a pcb)

$ uname -a
Linux mortimer 3.5.0-34-generic #55-Ubuntu SMP Thu Jun 6 20:18:19 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux

$ ldd Fritzing
        linux-vdso.so.1 =>  (0x00007ffff8e81000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f0383a62000)
        libQtSvg.so.4 => /usr/lib/x86_64-linux-gnu/libQtSvg.so.4 (0x00007f038380c000)
        libQtSql.so.4 => /usr/lib/x86_64-linux-gnu/libQtSql.so.4 (0x00007f03835cc000)
        libQtXml.so.4 => /usr/lib/x86_64-linux-gnu/libQtXml.so.4 (0x00007f0383388000)
        libQtGui.so.4 => /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (0x00007f03826dc000)
        libQtNetwork.so.4 => /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4 (0x00007f038239c000)
        libQtCore.so.4 => /usr/lib/x86_64-linux-gnu/libQtCore.so.4 (0x00007f0381ecb000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f0381cae000)
        libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f03819aa000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f03816ae000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f0381498000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f03810d7000)
        libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007f0380e9d000)
        libaudio.so.2 => /usr/lib/x86_64-linux-gnu/libaudio.so.2 (0x00007f0380c84000)
        libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007f038098d000)
        libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0 (0x00007f0380767000)
        libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007f03804cb000)
        libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007f038027b000)
        libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6 (0x00007f0380073000)
        libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6 (0x00007f037fe57000)
        libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x00007f037fc47000)
        libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007f037fa3d000)
        libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007f037f82b000)
        libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f037f4f0000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f037f2ec000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f037f0e3000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f0383cb6000)
        libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007f037eeba000)
        libXt.so.6 => /usr/lib/x86_64-linux-gnu/libXt.so.6 (0x00007f037ec53000)
        libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f037ea4f000)
        libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f037e812000)
        libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007f037e609000)
        libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f037e404000)
        libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f037e1e6000)
        libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f037dfdf000)

Original comment by bitsybof...@gmail.com on 19 Jan 2014 at 4:46

Attachments:

GoogleCodeExporter commented 9 years ago 
Just did a fresh build, and the top/bottom widget in the Inspector is present 
and works fine (using the sketch you uploaded). Your guess at this point is as 
good as mine--could it be different Qt versions?

uname -a
Linux j-VirtualBox 3.2.0-57-generic #87-Ubuntu SMP Tue Nov 12 21:35:10 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux

ldd Fritzing
    linux-vdso.so.1 =>  (0x00007fff09bff000)
    libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fa218c60000)
    libQtSvg.so.4 => /usr/local/Trolltech/Qt-4.8.5/lib/libQtSvg.so.4 (0x00007fa218a08000)
    libQtSql.so.4 => /usr/local/Trolltech/Qt-4.8.5/lib/libQtSql.so.4 (0x00007fa2187c6000)
    libQtXml.so.4 => /usr/local/Trolltech/Qt-4.8.5/lib/libQtXml.so.4 (0x00007fa218582000)
    libQtGui.so.4 => /usr/local/Trolltech/Qt-4.8.5/lib/libQtGui.so.4 (0x00007fa2178b4000)
    libQtNetwork.so.4 => /usr/local/Trolltech/Qt-4.8.5/lib/libQtNetwork.so.4 (0x00007fa217595000)
    libQtCore.so.4 => /usr/local/Trolltech/Qt-4.8.5/lib/libQtCore.so.4 (0x00007fa217096000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fa216e79000)
    libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fa216b78000)
    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fa21687c000)
    libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fa216666000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa2162a5000)
    libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007fa215fb0000)
    libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007fa215d13000)
    libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6 (0x00007fa215b0b000)
    libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6 (0x00007fa2158f1000)
    libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007fa2156e7000)
    libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007fa2154b0000)
    libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007fa21529f000)
    libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007fa214f6a000)
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fa214d65000)
    librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fa214b5d000)
    /lib64/ld-linux-x86-64.so.2 (0x00007fa218e8a000)
    libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fa21491f000)
    libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007fa21471a000)
    libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007fa2144f0000)
    libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007fa2142d1000)
    libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007fa2140ce000)
    libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007fa213ec7000)

Original comment by irasc...@gmail.com on 19 Jan 2014 at 6:27

GoogleCodeExporter commented 9 years ago 
It appears to be something in my Fritzing configuration folder 
(~/.config/Fritzing), if I close fz, move [the config folder out of the way and 
let Fritzing recreate it when it restarts then the drop down appears. 

I've zipped and attached my config folder in it's entirity.  Perhaps it's some 
custom part or something causing a conflict?

Original comment by bitsybof...@gmail.com on 19 Jan 2014 at 7:03

Attachments:

GoogleCodeExporter commented 9 years ago 
That was a very clever thought--it wouldn't have occurred to me. The top/bottom 
widget is missing, and the bug is cross-platform.

Original comment by irasc...@gmail.com on 19 Jan 2014 at 10:22

GoogleCodeExporter commented 9 years ago 
3 pin header parts in the uploaded config folder contained an empty layer 
property which overrides the default top/bottom behavior. r3b0dd5014eac ignores 
empty properties for the purposes of the Inspector.

Original comment by irasc...@gmail.com on 19 Jan 2014 at 11:55

GoogleCodeExporter commented 9 years ago 
Issue has moved to new issue tracker at github. Please continue the discussion 
at https://github.com/fritzing/fritzing-app/issues

Original comment by andre.knoerig@gmail.com on 23 Sep 2014 at 3:42