X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Sun, 26 Jul 2015 04:30:04 +0200 (CEST) X-X-Sender: igor2 AT igor2priv To: geda-user AT delorie DOT com X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu" From: gedau AT igor2 DOT repo DOT hu Subject: Re: [geda-user] pcb-rnd feature poll: please vote In-Reply-To: <201507260205.t6Q257OU004585@envy.delorie.com> Message-ID: References: <201507251534 DOT t6PFYRiK016181 AT envy DOT delorie DOT com> <201507260205 DOT t6Q257OU004585 AT envy DOT delorie DOT com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sat, 25 Jul 2015, DJ Delorie wrote: > If that includes specifying coordinates, then sweet :-) > >> I've just installed 20140306 (was that the last snapshot?) to test it. >> With the gtk hid, 'R' doesn't do anything. Report doesn't print length >> info either. > > Might be lesstif-only. :Report(NetLength) for gtk. Cool, thanks! Then I modify this point to add only the differences in some details I had in mind: - handle junctions (I already have most of graph buliding/handling the code because of mincut) - because of that, more integration with the GUI: lengths printed on the traces between junctions - I am not sure yet to what extent, but try to handle some of the corner cases: don't count overlapping traces twice, take poly/via/pin as a junction > >> Sometimes I scale down silk text and it becomes unreadable because the >> lines are just too thick. However, when I have larger text on the same >> board, I want lines to be thick. This feature would allow the user to >> change text line thickness independently of text size. > > Ok, but the silk lines are also limited by DRC minimum silk rules. I > find that that kicks in pretty quickly on small text. Clear, but I find DRC a differnet thing. Like you can make copper traces very thin on the UI and find them later with the DRC. Maybe someone just draws the design without worrying about DRC trying to get everything fit and determine the DRC rules at the end, when it's already clear how thin traces had to get. Heck, even text _lines_ work like that, I can set a high drc and then 's' them very thin. I just don't see why text lines should behave differently. > >> When I switched from autotools to scconfig, I didn't implement the >> detection of lesstif. > > Ah, ok. I thought you did something to bypass the HID api in a > gtk-specific way. No way, I really like the HID abstraction. >> Let's face it: the lesstif hid is not very popular, most users go >> for the gtk hid. > > True. I'm probably one of the only lesstif users. However, there's > also the batch HID that gedasymbols uses, and some day we should have > a Win32 HID. There's at least one other GUI hid out there in the wild > too. The batch HID does work in pcb-rnd. From time to time I am even daydreaming about developing an animator(1) based HID. I also agree that if "native look and feel" is important, a native HID is the way to go for win32. Regards, Igor2