Has anybody see this error where the icons at the top of the window
can't be found?
Attached is the error window.
System is Max OSX 10.5.6
Thanks,
Fred
Kingston Co.
fred...@sb.net
Error msg.pdf
Description: Adobe PDF document
___
geda-user maili
On Wed, 2009-01-28 at 23:53 +, Peter Clifton wrote:
> > > Give the works so far a try:
> > >
> > > http://repo.or.cz/w/geda-pcb/pcjc2.git
> > >
> > > git clone git://repo.or.cz/geda-pcb/pcjc2.git
> > > git checkout before_pours origin/before_pours
> >
> > git checkout -b before_pours origin
We have garchive in utilities, it should suffice.
i don't know it's current status, but i though it's purpose was to
make an archive of a project so that it could be "remade" or shared
easily across many folks
Hardkrash
On Jan 27, 2009, at 2:40 PM, Stefan Salewski wrote:
> Am Montag, den
On Wednesday 28 January 2009 09:27:28 pm Peter Clifton wrote:
> On Wed, 2009-01-28 at 19:59 -0500, Dan McMahill wrote:
> > Should I expect a speed improvement with GLX or just cool stuff like
> > layer transparency? I suspect that's a feature that won't take much use
> > before I say "how did I li
On Wed, 2009-01-28 at 19:59 -0500, Dan McMahill wrote:
> without looking at the code, is it feasible without major pain to have
> GL be a runtime selection?
I was thinking I'd split out the HID vtable callbacks into GTK / GL
versions, and #ifdef the HID setup.
Since the HID vtable can (I think)
Peter Clifton wrote:
> On Tue, 2009-01-27 at 21:17 +0100, Oliver Lehmann wrote:
>> Stefan Salewski wrote:
>>
>>> My one, shipped with gEDA 1.4.3 is tragesym version 0.0.12
>>> and dist-license and use-license is supported.
>> FreeBSD ports come with geda 20070216 which is probably a
>> svn/cvs/what
Peter Clifton wrote:
> On Wed, 2009-01-28 at 22:13 +, Peter Clifton wrote:
>> On Wed, 2009-01-28 at 01:11 +, Peter Clifton wrote:
>>> Give the works so far a try:
>>>
>>> http://repo.or.cz/w/geda-pcb/pcjc2.git
>>>
>>> git clone git://repo.or.cz/geda-pcb/pcjc2.git
>>> git checkout before_pou
On Wed, 2009-01-28 at 22:13 +, Peter Clifton wrote:
> On Wed, 2009-01-28 at 01:11 +, Peter Clifton wrote:
> > Give the works so far a try:
> >
> > http://repo.or.cz/w/geda-pcb/pcjc2.git
> >
> > git clone git://repo.or.cz/geda-pcb/pcjc2.git
> > git checkout before_pours origin/before_pours
On Wed, 2009-01-28 at 18:19 -0500, Dave McGuire wrote:
>I did have exactly those problems. I spent most of an afternoon
> digging through all of that, though, and I'm confident that I've
> gotten them resolved. The latest GTK (and friends) are compiled and
> installed, but anything tha
On Jan 28, 2009, at 6:14 PM, Peter Clifton wrote:
>>> I'm confused: I thought OpenSolaris used a GTK+-based GUI?
>>
>>It does. (well, more like "can") Thing is, the stuff it ships
>> with is kinda old, too old for later release of Cairo to use.
>> So...The resulting deluge of dependencies
On Wed, 2009-01-28 at 18:11 -0500, Dave McGuire wrote:
> > Please try the latest GTK+ 2.8.x point release, and see if that
> > works. It has
> > a lot less code than the very newest GTK+ release, so it should
> > have fewer
> > portability problems.
>
>I will; thank you for the suggestion
On Jan 28, 2009, at 6:06 PM, Peter TB Brett wrote:
>>> and versions of GLib/GTK+ since 2.4 are available for the vast
>>> majority of consumer operating systems and CPU architectures.
>>> AFAIK, it works
>>> on *at least* Solaris, Windows, Linux and BSD, on x86, x86-64, PPC
>>> and ARM.
>>
>>No
On Wednesday 28 January 2009 22:56:09 Dave McGuire wrote:
> > and versions of GLib/GTK+ since 2.4 are available for the vast
> > majority of consumer operating systems and CPU architectures.
> > AFAIK, it works
> > on *at least* Solaris, Windows, Linux and BSD, on x86, x86-64, PPC
> > and ARM.
>
>
On Jan 28, 2009, at 5:39 PM, Peter TB Brett wrote:
>>And actually, though, the portability problems that are giving me
>> heartburn lately are with gEDA, not PCB proper. GTK (and its thirty
>> or so dependencies) is a big pain in the ass for anyone who is not
>> running the absolute latest rel
On Wednesday 28 January 2009 19:51:48 Dave McGuire wrote:
>And actually, though, the portability problems that are giving me
> heartburn lately are with gEDA, not PCB proper. GTK (and its thirty
> or so dependencies) is a big pain in the ass for anyone who is not
> running the absolute latest
> Does it do Latin-1, or does it do raw octet streams and you get
> whatever your font gives you with them
It does raw octet streams with glyph lookups. It doesn't "support"
iso-latin-1 any more than it supports the cursor font, or zapf
digbats, or any other 8-bit font.
If you *happen* to give
>> - but pcb supports iso-latin-1 8-bit at the moment, aside from the
>> missing font issue.
> Its dangerous do document that we support iso-latin-1, lest anyone
> draws themselves fonts, and then gets cross if we decree in future,
> that PCB text is in UTF-8.
Does it do Latin-1, or does it do raw
On Wed, 2009-01-28 at 01:11 +, Peter Clifton wrote:
> Give the works so far a try:
>
> http://repo.or.cz/w/geda-pcb/pcjc2.git
>
> git clone git://repo.or.cz/geda-pcb/pcjc2.git
> git checkout before_pours origin/before_pours
git checkout -b before_pours origin/before_pours
^
On Wed, 2009-01-28 at 15:51 -0500, DJ Delorie wrote:
> Our default font is 7-bit.
>
> I agree that UTF-8 will be the *only* expansion option we'll take when
> we get to that point - but pcb supports iso-latin-1 8-bit at the
> moment, aside from the missing font issue.
Its dangerous do document t
Thanks for the bug report. I just updated the wiki page.
Stuart
On Wed, 28 Jan 2009, Kipton Moravec wrote:
> http://geda.seul.org/wiki/geda:faq-attribs?s=bom
>
> I wanted to make a BOM so I cut and pasted the command example, and it
> did not work.
>
> gnetlist -g partlist3 -o output.bom schem
http://geda.seul.org/wiki/geda:faq-attribs?s=bom
I wanted to make a BOM so I cut and pasted the command example, and it
did not work.
gnetlist -g partlist3 -o output.bom schematic.sch
Took a couple of minutes to figure out, but it did not like the
"partlist3" it should be "partslist3" (was mis
> Changing the internal units of PCB is not practical at this time. I
> think we calculated we'd need to maintain micrometer precision to
> preserve the old "high resolution" units. That means absolutely no
> more 16-bit coordinate values (oh, darn! ;) and we'd have to be a lot
> more careful ab
> I think result was that 1nm (nanometre) base-unit should work perfectly.
> (in my opinion larger units may work good, if rounding is smart.)
Er, right - nanometer, not micrometer. That limits board sizes to
about 2.1 meters if we want to avoid signed-unsigned problems with 32
bit integers.
_
> Right now, we can cheat and pretend we never supported non 7-bit
> ASCII characters. If we add any support for 8bit code-pages, we'll
> be stuck having to support those, _and_ UTF-8 in the future.
Right now we support *uncoded* 8-bit characters and a 256 (er, 255 due
to NUL-terminated strings)
Am Mittwoch, den 28.01.2009, 20:36 + schrieb Peter Clifton:
>
> Didn't we come to the view at some point, that using a sufficiently
> small metric unit internally would work fine?
>
> (Due to the definition of 1" = 2.54cm allowing us to precisely specify
> both metric and imperial units, give
> Didn't we come to the view at some point, that using a sufficiently
> small metric unit internally would work fine?
>
> (Due to the definition of 1" = 2.54cm allowing us to precisely specify
> both metric and imperial units, given a sufficiently small metric unit?)
Changing the internal units
On Wed, 2009-01-28 at 15:21 -0500, DJ Delorie wrote:
> > I'm not sure if PCB supports UTF-8 text, but if not.. doing that would
> > make a good start.
>
> It doesn't. It does support iso-latin-1 but the default font only has
> ASCII characters in it. Someone would have to draw an eight-bit font.
On Wed, 2009-01-28 at 15:21 -0500, DJ Delorie wrote:
> > > Metric-only library. (it's imposibble, i know :))
> >
> > Not _im_possible.. so long as its a very very small metric unit which
> > gets used.
>
> It's not practical, either, unless you only have metric parts.
Didn't we come to the view
Would people please change the subject line of their emails before
forking a massively off topic discussion from the original thread.
Really, I'm not interested in reading about C++ from non PCB developers,
nor having to sort it out from the survey results people are sending.
Thanks,
--
Peter C
On Jan 28, 2009, at 3:15 PM, DJ Delorie wrote:
>>Theoretically speaking, I agree, but I (like you, I suspect)
>> compile software all the time...and if something is written in C++,
>> that tends to about triple the chances of my having to spend all damn
>> afternoon getting it built.
>
> I susp
Thanks, I didn't click the radio button for that layer.
On Wed, Jan 28, 2009 at 3:26 PM, DJ Delorie <[1...@delorie.com> wrote:
Are you drawing on a non-visible layer?
Other than that, what you're doing I do all the time - and it
always
works for me.
___
On Jan 28, 2009, at 3:19 PM, al davis wrote:
>>And again, I agree in theory, but in practice things are
>> quite a bit different. A lot of people writing C++ code
>> these days have no idea what they're doing, and the rest of
>> us pay the price in frustration when we try to get something
>>
Are you drawing on a non-visible layer?
Other than that, what you're doing I do all the time - and it always
works for me.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
What would be keeping me from drawing a line in PCB where there's no
component? I'm just trying to connect one pin to another. When I
click on the end of a line I'll get the ghost line and when I click to
place the trace the ghost line (trace) will vanish.
_
> I'm not sure if PCB supports UTF-8 text, but if not.. doing that would
> make a good start.
It doesn't. It does support iso-latin-1 but the default font only has
ASCII characters in it. Someone would have to draw an eight-bit font.
In theory, you could put in whatever eight-bit font you want
On Wed, 28 Jan 2009 20:44:12 +0100
Oliver Lehmann wrote:
> No OpenGL support for many ATI cards on FreeBSD because no native
> drivers and the open source ones are mostly lacking support. No idea
> how good the binary nvidia driver works...
I have a GeFORCE (was that the right name?) and am usin
On Wednesday 28 January 2009, Dave McGuire wrote:
> And again, I agree in theory, but in practice things are
> quite a bit different. A lot of people writing C++ code
> these days have no idea what they're doing, and the rest of
> us pay the price in frustration when we try to get something
>
> >>You have Motif too, and it's possible to write new HIDs for PCB.
> > I know/ I try use he, but he dont look stable :(.
>
>Really? I didn't know that. I thought it was being maintained in
> parallel with the GTK HID.
Not in parallel - I maintain the motif (lesstif) HID, Dan (I thi
> A lot of people writing C++ code these days have no idea what
> they're doing,
Yes, that's the key point - C++ makes it easier to do bad things wrt
portability, but it's nothing that C doesn't also *allow*. The C
programmers have had more experience with portability, that's all.
>Theoretically speaking, I agree, but I (like you, I suspect)
> compile software all the time...and if something is written in C++,
> that tends to about triple the chances of my having to spend all damn
> afternoon getting it built.
I suspect that's a problem with the choice of externa
On Wednesday 28 January 2009 19:54:19 Ben Jackson wrote:
> On Wed, Jan 28, 2009 at 02:46:16PM -0500, Dave McGuire wrote:
> >If you write a QT HID, I will definitely try it. Please don't
> > suggest moving PCB to C++ though. =)
>
> One of these days when I'm bored and looking for a programming
On Jan 28, 2009, at 2:54 PM, Ben Jackson wrote:
>>If you write a QT HID, I will definitely try it. Please don't
>> suggest moving PCB to C++ though. =)
>
> One of these days when I'm bored and looking for a programming project
> I am going to rewrite it in C++. You could carve a "libpcb++" ou
On Wednesday 28 January 2009 19:46:16 Dave McGuire wrote:
> >>You have Motif too, and it's possible to write new HIDs for PCB.
> >
> > I know/ I try use he, but he dont look stable :(.
>
>Really? I didn't know that. I thought it was being maintained in
> parallel with the GTK HID.
GTK HID
On Wed, Jan 28, 2009 at 02:46:16PM -0500, Dave McGuire wrote:
>
>If you write a QT HID, I will definitely try it. Please don't
> suggest moving PCB to C++ though. =)
One of these days when I'm bored and looking for a programming project
I am going to rewrite it in C++. You could carve a "
On Jan 28, 2009, at 11:45 AM, al davis wrote:
and C++?
>>>
>>>NOO! We have enough portability problems as it is.
>>
>> At this point, I don't think C++ would reduce portability.
>> Actually, since C++ is a more standard-requiring language,
>> it might even help.
>
> I agree with DJ.
On Jan 28, 2009, at 11:24 AM, DJ Delorie wrote:
>>> and C++?
>>
>>NOO! We have enough portability problems as it is.
>
> At this point, I don't think C++ would reduce portability. Actually,
> since C++ is a more standard-requiring language, it might even help.
Theoretically speaking,
On Jan 28, 2009, at 2:38 PM, Alexander Gvozdev wrote:
>> On Jan 27, 2009, at 7:56 PM, Alexander Gvozdev wrote:
>>> Many people want "jump-up" from "ugly" GTK.
>>
>>You have Motif too, and it's possible to write new HIDs for PCB.
> I know/ I try use he, but he dont look stable :(.
Really? I
Peter Clifton wrote:
> Hi guys,
>
> Could anyone interested in seeing / using a GL version of PCB, please
> respond to this message privately - directly to me (or on-list if you
> don't have my email address).
No OpenGL support for many ATI cards on FreeBSD because no native drivers
and the open
On Wednesday 28 January 2009 03:57:33 Dave McGuire wrote:
> On Jan 27, 2009, at 7:56 PM, Alexander Gvozdev wrote:
> > Many people want "jump-up" from "ugly" GTK.
>
>You have Motif too, and it's possible to write new HIDs for PCB.
I know/ I try use he, but he dont look stable :(.
>
> > What abou
On Wednesday 28 January 2009 01:11:08 Peter Clifton wrote:
> On Wed, 2009-01-28 at 00:56 +, Alexander Gvozdev wrote:
> > I'm maintain pcb for pan-russia/ukrainian/belorussian distro (AltLinux).
> > Many people want "jump-up" from "ugly" GTK.
>
> Still just as ugly for now ;)
>
> > I may test pc
Stefan Salewski wrote:
> Am Mittwoch, den 28.01.2009, 09:43 -0800 schrieb Joerg:
>
>> Unfortunately most CAD system do that and rotate it all (Eagle does it,
>> too). Kind of a nuisance but often I create two symbols, one rotated and
>> one not. Then I don't have to go through all the mouse clic
Am Mittwoch, den 28.01.2009, 09:43 -0800 schrieb Joerg:
> Unfortunately most CAD system do that and rotate it all (Eagle does it,
> too). Kind of a nuisance but often I create two symbols, one rotated and
> one not. Then I don't have to go through all the mouse clickaroo to
> unrotate descripto
Am Tue, 27 Jan 2009 20:51:00 +
schrieb Peter Clifton :
> Hi guys,
>
[... snip ...]>
> glxinfo > glxinfo.txt
please see attachment
[... snip ...]
> I's also be curious to know what kind of numbers you get running
> "glxgears".. (ok - technically glxgears isn't a good benchmark, but
> never
Kai-Martin Knaak wrote:
> Hi,
>
> when working with gschem, I next to never want rotated text. However, by
> default attributes seem to stick to the graphics and rotate with it. I
> find myself unrotating the text after I rotated the symbol by 90°. An
> alternative is to select the graphics onl
Hi,
when working with gschem, I next to never want rotated text. However, by
default attributes seem to stick to the graphics and rotate with it. I
find myself unrotating the text after I rotated the symbol by 90°. An
alternative is to select the graphics only. But this requires many mouse
cli
On Wednesday 28 January 2009, DJ Delorie wrote:
> > > and C++?
> >
> > NOO! We have enough portability problems as it is.
>
> At this point, I don't think C++ would reduce portability.
> Actually, since C++ is a more standard-requiring language,
> it might even help.
I agree with DJ.
The
> > and C++?
>
>NOO! We have enough portability problems as it is.
At this point, I don't think C++ would reduce portability. Actually,
since C++ is a more standard-requiring language, it might even help.
___
geda-user mailing list
geda-use
> DJ might just design a keyboard with keys as small as 1005s just to
> see who could use it.
What, you don't like a challenge?
Now, a keyboard made with those new OLED keys...
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/c
On Wed, 2009-01-28 at 23:40 +1100, Hamish Moffatt wrote:
> Hi,
>
> I'm a bit confused about what's needed/expected here.
>
> For the lenny release we can only expect to fix RC bugs at this time.
> This means the copyright/licensing fix, and possibly taking the most
> critical stuff from 1.4.3 and
Am Mittwoch, den 28.01.2009, 01:25 +0200 schrieb Robas, Teodor:
>
>Shure some people would want standard keyboard accelerators, but IMO
>this
>isn't working well even for standard applications. A simple example:
>krusader (Ctrl+S) vs. eclipse (Ctrl+F or Ctrl+H). And EDA software is
On Wed, 28 Jan 2009 00:56:05 +, Alexander Gvozdev wrote:
> Many people want "jump-up" from "ugly" GTK.
Beauty is in the eye of the beholder.
Me, I am all in favor of GTK look and feel.
---<(kaimartin)>---
--
Kai-Martin Knaak tel: +49-511-762-2895
Universitä
61 matches
Mail list logo
