Tiny little bug in eeschema: when you set the height of a sheet pin text, it
actually sets the width, and vice versa.
diff --git a/eeschema/sheetlab.cpp b/eeschema/sheetlab.cpp
index 9f90792..8a10319 100644
--- a/eeschema/sheetlab.cpp
+++ b/eeschema/sheetlab.cpp
@@ -94,8 +94,8 @@ int SCH_EDIT_FR
Ok. I'm understood.
14.04.2015 20:55, jp charras пишет:
Le 14/04/2015 18:30, Eldar Khayrullin a écrit :
Repeat.
P.S. May be previous mail was dissapear
11.04.2015 13:10, Marco Ciampa пишет:
I do not why but I just noted that in Eeschema (last build)
Preferences->Hotkeys->Edit hotkeys
first
Le 14/04/2015 18:30, Eldar Khayrullin a écrit :
> Repeat.
> P.S. May be previous mail was dissapear
>
> 11.04.2015 13:10, Marco Ciampa пишет:
>> I do not why but I just noted that in Eeschema (last build)
>>
>> Preferences->Hotkeys->Edit hotkeys
>>
>> first two tabs titles are not nationalized (Co
Repeat.
P.S. May be previous mail was dissapear
11.04.2015 13:10, Marco Ciampa пишет:
I do not why but I just noted that in Eeschema (last build)
Preferences->Hotkeys->Edit hotkeys
first two tabs titles are not nationalized (Common & Schematic Editor) the last
is ok.
--
Marco Ciampa
I kno
Application: kicad
Version: (2015-04-13 BZR 5596)-product Release build
wxWidgets: Version 3.0.2 (debug,UTF-8,compiler with C++ ABI 1002,GCC
4.2.1,STL containers,compatible with 2.8)
Platform: Mac OS X (Darwin 14.1.0 x86_64), 64 bit, Little endian, wxMac
Boost version: 1.54.0
USE_WX_GRA
> It's worth looking at the documentation for the smart pointer used:
> http://www.boost.org/doc/libs/1_57_0/libs/smart_ptr/shared_ptr.htm
> The last thing I want to do is make your life harder by confusing you,
> so please carry on asking questions if it still doesn't make sense for
> you. The 3
On 14 April 2015 at 09:17, Mário Luzeiro wrote:
> Hi Mark,
>
> No problem, I didn't know how it works but now I understand it.
>
> I was thinking that they have some documentation or rules /guides like the
> MISRA C/C++
> http://www.misra-cpp.com
> http://en.wikipedia.org/wiki/MISRA_C
>
> They de
Le 14/04/2015 11:08, Mário Luzeiro a écrit :
> Hello Jean-Pierre,
>
>
>>> What about apply the remove holes only to that "10 000 to 20 000
>>> corners" (I believe the remove holes will so create more
>>> corners..with the format of the hole..) and then render an outline
>>> with the approximation
Hello Jean-Pierre,
>> What about apply the remove holes only to that "10 000 to 20 000
>> corners" (I believe the remove holes will so create more
>> corners..with the format of the hole..) and then render an outline
>> with the approximation polygon.?
>It could work for via holes, not pad holes
Hi Mark,
No problem, I didn't know how it works but now I understand it.
I was thinking that they have some documentation or rules /guides like the
MISRA C/C++
http://www.misra-cpp.com
http://en.wikipedia.org/wiki/MISRA_C
They describe all the rules with examples and cases (the original documen
Thanks Mark it works.
I think a quick summary of the main occurrences can be extracted:
High impact:
Resource leaks
Memory - corruptions
Memory - illegal accesses
Uninitialized variables
Medium impact:
Uninitialized members
Control flow issues
Null pointer dereferences
Incorrect expression
Integ
On Mon, Apr 13, 2015 at 09:57:55PM +0100, Brian Sidebotham wrote:
> I sync'd with Marco's repo so that's now reflected in my repo.
>
> I just need to do the po update stuff I think and then I'll do a pull
> request to get the repo's aligned.
Trerrific, many thanks! I am studying cmake to be able
12 matches
Mail list logo
