Re: gEDA-user: package library, or include in schematic
On Mon, Sep 03, 2007 at 08:54:38AM +0200, Duncan Drennan wrote: > Is there a way for gschem to package a library for a set of > schematics, or possibly include the symbols in the schematic file > itself? Under edit, 'embed component' All of the .sch's I post are embedded to simplify things. (though I'm not sure anyone has downloaded any of the ones I've posted, I appreciated finding examples when I was getting started so I made them available) -- Ben Jackson AD7GD <[EMAIL PROTECTED]> http://www.ben.com/ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: package library, or include in schematic
Is there a way for gschem to package a library for a set of schematics, or possibly include the symbols in the schematic file itself? I'm sure I saw some option to this effect somewhere, but I can't find it any more ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: schematic messed up
> I tried this sch snippet on my current git build and it seems like the > capacitor and gnd symbols are properly connected for me. Can you send > me a screenshot of a gschem where things aren't lined up. Maybe this > is a cygwin only problem? I think the real problem is with the libraries somewhere. I'll look into this a bit more carefully (I was tired and in a rush when this cropped up) and see if I can figure out the root of the issue. Thanks, Duncan ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Polygon over polygon pour
On Mon, Sep 03, 2007 at 06:17:53AM +0100, ST de Feber wrote: > > I'd like to pour a polygon over a smaller polygon and > want the smaller one to be cleared through like lines > can do with the toggle ! > > Is that possible ? Looking at the source, I'd say no. There's no "plow" code for polygons, so a poly would never be removed from another poly. If you draw a line in the shape of a box around the area, it will clear out the area. Beware that when you orphan areas of a polygon like that, the largest remaining area is the one that survives. You can get odd effects when a large portion of your polygon is hidden (eg you add a component to the surviving side and it shrinks enough that another island becomes dominant). -- Ben Jackson AD7GD <[EMAIL PROTECTED]> http://www.ben.com/ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: Polygon over polygon pour
Hello list, I'd like to pour a polygon over a smaller polygon and want the smaller one to be cleared through like lines can do with the toggle ! Is that possible ? grtz Simon ___ Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: gEDA/gaf stable version 1.2.0-20070902 released!
Hi, I am pleased to announce the second major stable release of gEDA/gaf: 1.2.0-20070902. This release rolls up the changes from the last 2 months of development. Many thanks to everybody involved. You can find this release at: Release Notes: TBD Download: http://geda.seul.org/release/v1.2/1.2.0 I will write up release notes and send them out soon. Enjoy, -Ales PS. md5sum's for this release: bbd67ab610a41bf44716cfdc651c0eb8 *geda-docs-1.2.0.tar.gz ca177c15be955876c87095a84658e0ff *geda-examples-1.2.0.tar.gz 39acaa05c12c78f5a1fece22760e9d91 *geda-gattrib-1.2.0.tar.gz fe435c8124df5ee85e46f3f1e329ff70 *geda-gnetlist-1.2.0.tar.gz 2bd5b949f0579bd5bc8dc91d6ddfd8cd *geda-gschem-1.2.0.tar.gz bf23cf68e82f14f1e44b83fa9b951b90 *geda-gsymcheck-1.2.0.tar.gz cbbab791d2e9557513da2fbb2c40ba19 *geda-symbols-1.2.0.tar.gz 7430311688713ae4e924344970deecc5 *geda-utils-1.2.0.tar.gz 43f2b2daabee59ffeae84fe13c10c51d *libgeda-1.2.0.tar.gz 7541ea3f918103e9dfef5f8f25fc597f *Makefile 85b7e894dfa8a393224bf77f61b3e900 *README ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: alarm clock boards are in!
Ah, good point. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: alarm clock boards are in!
On Aug 31, 2007, at 5:56 PM, DJ Delorie wrote: > >> Ahhh, i see, i forgot they were boasting a new method for design >> entry > > Yup, "no touch". I suspect if I called them, I wouldn't get the cheap > price. They are friendly to work with if you tell them that there is an issue with the no-touch they would probably fix it. That's what I was saying. Steve > > > ___ > geda-user mailing list > geda-user@moria.seul.org > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: list of cell types emitted by icarus synthesis?
Stephen Williams <[EMAIL PROTECTED]> writes: > An approximation of the answer you are looking for is to look > in the ivl_target.h header file. This will show all the different > types of gates might be passed to the edif code generator. Of > course, not all those gates are necessarily actually generated > in a synthesized result, but you'll at least get an idea. Thanks, Stephen. In particular, do you mean the entries in the ivl_logic_t enum? That shouldn't be hard at all, although I don't see adders in there, and Icarus seems to emit adder cells (ADD8), which don't seem to be accounted for in that structure... I was just wondering what other sorts of stuff like this might crop up before I release anything. - a ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: schematic messed up
Hi, > > Please post a small schematic fragement from the older version > > of gEDA/gaf that shows this problem. > > v 20070216 1 > > N 44800 48000 44800 48100 4 > N 45800 48100 45800 48000 4 [snip] I tried this sch snippet on my current git build and it seems like the capacitor and gnd symbols are properly connected for me. Can you send me a screenshot of a gschem where things aren't lined up. Maybe this is a cygwin only problem? -Ales ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: reload library directories while in gschem
Hi, [snip] > Is there any way to reload the directories while in gschem, or is > restarting the only option? > Unfortunately, these is no update mechanism when you are using component-library-search, so a restart is required. However, if anybody wants something to do, then extending the refresh button to update the component libraries found by component-library-search might be an interesting patch. -Ales ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: customise mouse scroll action
> So try replacing the undo lines with:
>
> ("Control z" . edit-undo)
> ("Control y" . edit-redo)
>
Having these standard keybindings is actually a good idea, so I have them
in my local git repository, soon to be pushed to master.
I left the other undo/redo keybindings in just in case people are actually
using those too.
Thanks,
-Ales
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb: gui-dialog-print.c weirdness?
On Sun, 02 Sep 2007 16:59:52 -0400 Dan McMahill <[EMAIL PROTECTED]> wrote: > > No, quite the opposite. ghid_dialog_print() is obsolete and I haven't > gotten to replacing it with ghid_attribute_dialog yet. BTW, > ghid_attribute_dialog is in fact used by the printer calibration. > Search for gui->attribute_dialog. > > I have a couple of patches which touch ghid_attribute_edit too that I > haven't checked in. Mostly they are needed to let me get rid of the > ghid_dialog_print() function. I'm hoping to get that done over the > next few days, but I can't promise that. ghid_dialog_print() will > probably go away at that time since it is less general purpose. > Ok, I'll wait for those patches to land in CVS then. In the meantime I can figure out how to make notebooks to work in the lesstif HID. Hans > -Dan > > > ___ > geda-user mailing list > geda-user@moria.seul.org > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user > -- $ cat .sig /dev/null ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb: gui-dialog-print.c weirdness?
Hans Nieuwenhuis wrote: > Hi, > > My apologies if this too off-topic for this list but I have a question > about two functions in gui-dialog-print.c in pcb. > > I am trying to implement some GUI attributes in the HID_attributes struct > (after some discussion with DJ the other day). Up until now I and quite > successful in doing that, see the screenshot below: > > http://www.xs4all.nl/~vzzbx/files/ps-export.jpg > > One thing is baffelling me, in the aforementioned file there is a > function ghid_dialog_print (which I have modified) and the function > ghid_attribute_dialog (not modified). Apart from one mention in the HID > structure in gtkhid-main.c the latter never seems to get called. Both > functions seem to do the same besides having different call parameters. > > The export dialog seems to work fine in all cases I tested: > - export through menu > - export in batch mode > > Is ghid_attribute_dialog() obsolete and would it be better if removed? I > can also just copy my changes from ghid_dialog_print() to > ghid_dialog_print(), but that feels not like the right thing(TM). No, quite the opposite. ghid_dialog_print() is obsolete and I haven't gotten to replacing it with ghid_attribute_dialog yet. BTW, ghid_attribute_dialog is in fact used by the printer calibration. Search for gui->attribute_dialog. I have a couple of patches which touch ghid_attribute_edit too that I haven't checked in. Mostly they are needed to let me get rid of the ghid_dialog_print() function. I'm hoping to get that done over the next few days, but I can't promise that. ghid_dialog_print() will probably go away at that time since it is less general purpose. -Dan ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: pcb: gui-dialog-print.c weirdness?
Hi, My apologies if this too off-topic for this list but I have a question about two functions in gui-dialog-print.c in pcb. I am trying to implement some GUI attributes in the HID_attributes struct (after some discussion with DJ the other day). Up until now I and quite successful in doing that, see the screenshot below: http://www.xs4all.nl/~vzzbx/files/ps-export.jpg One thing is baffelling me, in the aforementioned file there is a function ghid_dialog_print (which I have modified) and the function ghid_attribute_dialog (not modified). Apart from one mention in the HID structure in gtkhid-main.c the latter never seems to get called. Both functions seem to do the same besides having different call parameters. The export dialog seems to work fine in all cases I tested: - export through menu - export in batch mode Is ghid_attribute_dialog() obsolete and would it be better if removed? I can also just copy my changes from ghid_dialog_print() to ghid_dialog_print(), but that feels not like the right thing(TM). Thanks, Hans -- $ cat .sig /dev/null ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: TV card question
Hi, >Here's a question for the MythTV experts in the group. [snip] You may want to post these questions to the MythTV users group. I'm sure there are more MythTV experts there. Whoa, that seems like quite a lively list based on the archives. http://www.mythtv.org/mailman/listinfo/mythtv-users/ Thanks, -Ales ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: TV card question
Hello everyone: Here's a question for the MythTV experts in the group. Here's the background - I had a Hauppage TV card (which I used for video capture) running fine under Mandrake 10. Then the system's motherboard died, taking the Hauppage card with it. I recreated the system on a new mobo, installing Mandrake 2005 (mainly because I had a set of those CD's laying around.) So I got everything reinstalled and working on that. I just needed a new TV card. I recently purchased a Hauppage PVR-150, and although the system detects its presence, the card won't work. I've downloaded IVTV drivers for my kernel (the old 0.49 versions for 2.6.11) and those load without error, but will not talk to the card. All of the "how to" instructions I've found so far say you should test by doing a "cat" from /dev/video0. The problem is that on my system this device doesn't exist. One of the "how to" documents said you could create the /dev/video* devices manually, which I tried, but they were gone after reboot. So I imagine that udev (if I understand its purpose correctly) isn't seeing the card. Do you think this might indicate that the Hauppage might be bad? Another bit of info: this is a dual-boot system, with Windows 98 on the other partition. I tested the previous TV card first under Windows, and it worked right away. But the drivers that came with the PVR-150 are for XP, so although Windows detected and identified the card correctly, the drivers wouldn't install. After some searching, I downloaded a driver that might _possibly_ be right for the PVR-150 (it was supposed to support all cards with its particular chipset), but they didn't work either. When I try to start WinTV 2000 it says it can't find some sort of filter device. That could mean the card's bad, I suppose, or it could just be the wrong driver. I'm thinking I may be missing some video components on Linux, since it doesn't create /dev/video* and I haven't tried a TV card before on this install. But it doesn't seem likely, as I've downloaded and installed the many, many video-related packages to get Xine working. But I'm still hopeful that I won't have to return this card. Any suggestions of video-type packages that I might have missed? (I suppose I could try upgrading to kernel 2.6.18 as the IVTV docs suggested, so I can get more recent drivers, but I think my problem is more fundamental than that.) Thanks, Vaughn ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Footprint naming convention
On 9/1/07, andrewm <[EMAIL PROTECTED]> wrote: > I am presently drawing up footprints for my stock components. > > I have read the naming conventions for the footprints and have > done some searches but can't find an answer to this query. > > I have for many components two different foot prints. I would > like to know if there is a convention to naming the multiples. > > I don't mean I have a device that comes in a DIP40 and also > comes in a TQFP44. I mean I wish to have two version of a > MSSOP28W (0.65mm 28 lead 5.3mm wide package) > footprint. > > I would like one version of the footprint following the > manufacturer approved pin width/length. I would also like > another version with longer pins that I use in prototype > boards that I will hand solder. If you followed a manufacturer's specification I would use a suffix that calls out the specific manufacturer and package designation (e.g. "__TI_DRC_Package") IPC-7351 calls out an environment use suffix which you could probably use for designating larger prototype pads. The "Most Material" condition may work for your prototype fooprints and the "Nominal Material" for a production process. M ... Most Material N ... Nominal Material L ... Least Material I am thinking of adding the suffixes "MM", "NM", "LM" to my naming convention to correspond to the IPC-7351 material conditions. (* jcl *) -- http://www.luciani.org ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Units used by software
>> andrewm wrote: >> >> If it's not been done by anyone already I am going >> to just write some kind of parser that does it for >> me external. > DJ Delorie wrote: > Sounds like a useful tool. Teach it to allow > overrides on a per-value basis (like my 2pad script > does). I.e.: > > Pin[0.2 0.2 0.5 0.2 0.2 10mil 0.1] > > Hmm^2... teach pcb's parser to support a unit suffix > on each value! We only need mil and mm, but the > mechanism should allow for more as needed. It won't > *save* that way, but it lets you read in footprints > with human-simpler values. OK - well I am not very bright and the chances of me modifying the code tree for PCB without breaking something are slim to none. So I shall do it external. I will public the code, however I would have to prefix it with a warning that veiwing my C style may cause people to run away screaming "my eyes my eyes". It really is that ugly. If no one has any better suggestions I am going to make it take one input file read-modify-write it. Any line in the file that has a dimension suffix it will comment out, add a comment line to say it is autogenerated and then put the computer readable centimil version. Eg. pin[0.2mm 0.2 0.5 0.2 0.2 10mil 0.1mm] in the file would end up #pin[0.2mm 0.2 0.5 0.2mm 0.2mm 10mil 0.1mm] # The following line was automatically generated pin[7874 7874 19685 7874 7874 1000 3937] That should mean that you can un-comment the old version and try again if you made a mistake. I will make it so that you only need to sufix the unit if it changes. In the example above only the first dimension had a sufix until the units changes at 10mil and then the next metric after that one needed a sufix again. Or is this getting to complex to document for people ? (it's trivial code wise but may cause headaches in terms of noob questions) Finaly any objections to mm = Millimeter um = Micrometer mil = thousanth of an inch cmil = 100 thousanth of an inch ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
