Hello Alex,
I had the same issue compiling with boost 1.67.0.
Compiling with boost 1.69 did not have the issue on my machine (Linux)
May be a change in the cmake files in order to detect older boost
versions is needed.
Cheers,
Dino.
On 16/07/21 13:39, Alex Vidrasan wrote:
Hi,
I tried t
Hi all,
May be this should be into bug reports, but since I've seen some mail
about this argument directly here, I just answer to those. If I have to
file a bug report (if it really is a bug and I did not just miss some
environment variable to be set) please let me know.
Compiling and insta
input lines and 4
output signals. I want to connect all output signals to a bus.
I have tried several combinaisons without any success. How can I
connect these busses to a largest bus ?
Did you use the tools->bus definition to define the bus type?
Cheers,
Dino Ghilardi.
My
No more build error on my machine (gcc 6.3.0)
Cheers,
Dino.
On 10/06/20 14:52, Jeff Young wrote:
I’ve merged an attempted fix. (Of course the previous one compiled fine on
CLang too, so I’m not 100% confident in it -- but it seem to fit the error GCC
was generating.)
On 10 Jun 2020, at 12
Congratulations Eeli and Simon!
Dino.
On 04/02/20 10:40, Seth Hillbrand wrote:
Welcome to our newest Bug Squad members Eeli Kaikkonen and Simon
Richter. As members of the Bug Squad, they help to verify, triage and
classify our bug reports, serving a critical role in ensuring KiCad
continues
Did you also try with "git clean -fx"
to delete the old auto-generated and non-tracked files that can lie
around from old versions?
Cheers,
Dino.
On 14/01/20 21:19, Ian McInerney wrote:
Marco,
Delete every file inside include/ that ends with "_lexer.h" (note, don't
delete the dsnlexer.h fi
Hello Todor,
You should find issues for kicad on gitlab on:
https://gitlab.com/kicad/code/kicad/issues
Best regards,
Dino.
On 14/01/20 09:39, Todor Todorov wrote:
Hello all,
I have been trying to access the bug tracker for KiCad under
https://launchpad.net/kicad for the last couple
On 23/11/19 10:05, Alexander Shuklin wrote:
Hi Dino,
I would say "back annotation" and "geographical annotation" are just
different things. We with Brian plan to implement both of them.
Basically when you want to get references from board and apply them to
corresponding schematic, that back annot
On 22/11/19 23:14, Andy Peters wrote:
On Nov 22, 2019, at 2:30 PM, Dino Ghilardi wrote:
Just my two cents on this.
Considering that the actual "manual work-around" to do the "back annotation"
now can be:
-Open pcbnew and eeschema at the same time
-Select the componen
Just my two cents on this.
Considering that the actual "manual work-around" to do the "back
annotation" now can be:
-Open pcbnew and eeschema at the same time
-Select the component you want to rename on pcbnew
-the right symbol gets highlighted (but not selected) automatically in
eeschema
-se
Hello,
Latest commit (master branch) is not compiling giving an
"undefined reference to `PgmOrNull()'" error during make
I tried also using:
git clean-fx
make clean
cmake ../
make -j7
may be something is missing from the commit?
Platform: Debian Linux.
Commit 0a829c328e90f550994a7660b310630a5a
On 20/09/19 20:55, Wayne Stambaugh wrote:
Initially it will be simple DNF marking. Eventually full variant
support will be included. It's hard to say when that might happen.
There are a lot of new features planned for the new schematic file
formats some of which will most likely have priority
+1 on this
I usually work-around the problem setting the component value to "NM" or
"Not mounted" or "Don't mount" , but this is sub-optimal and needs more
work to update the bom and the place files.
The only suggestion I have is to make translatable or configurable the
shown string on the s
Hallo everybody,
Now that the old (sub)string related to the commit that has been
compiled is not in the version string anymore, may be it should be added
somewhere in the "version info" dialog to have that information easily
available in the bug reports.
P.S.: If this has yet been discussed.
" gave to me the same
results.
Cheers,
Dino.
On 1 Aug 2019, at 01:14, Dino Ghilardi wrote:
Hi Jeff,
On Linux (debian) looks good (a kind of light blue) until you don't
select the same blue as background color, so this seems a good default, but
having it configurable in the co
Hi Jeff,
On Linux (debian) looks good (a kind of light blue) until you don't
select the same blue as background color, so this seems a good default,
but having it configurable in the color selection will help in that case
(consideried also that load/save of color schemes is coming soon).
A
Hi Alexander,
>
> Maybe that's not too bad, as far as I remember, copper layers are
> polygons with get area method already implemented. But for sure that
> will take hours for debug.
>
A little bit of "brainstorming":
copper layer weight:
For the covered area extimation one possible way could
ul 22, 2019 at 9:39 PM Alexander Shuklin <
>> jasura...@mail.ru >
>> wrote:
>> >>
>> >> Damn ><,
>> >> don't use last patch, please.
>> >> It doesn't count total vias amou
s quite like the "Edit Symbol Fields" dialog. I would suggest
to extend this one instead of creating your own one.
What I would like to see is an advanced search for components, having at
least the filter features of cvpcb. This would allow ditching the
redundant dialogs for symbol
Also as an example of possible U.I. for search, including common, simple
and advanced options.
https://www.youtube.com/watch?v=QCMddxkKe8k
(starting around 0:18 of the video).
Cheers,
Dino.
On 26/07/19 23:21, Jeff Young wrote:
Oh cool. I’ll look into it….
On 26 Jul 2019, at 14:57, Wayne
personally I'd like being able to use full regular expressions, so that
the new user can use the asterisk, more advanced users can use more complex
expressions to better filter the results.
Il Ven 26 Lug 2019 20:45 Jon Evans ha scritto:
> Another way to solve this is the Google approach: matc
On version tagged 5.1.3 I'm unable to drag vias with the "D" shortcut
(drag 45 degrees), is it a bug or a new feature? (I did not see any
option like "consider all vias locked while dragging", so I suppose this
behaviour is not intended).
Do I have to file a bug report on launchpad?
Cheers,
vior on different systems? I use
archlinux x64 OS.
there's screenshot in attachment
2) Can we use something like _( "Height" ) + ":" for translation, not _(
"Height:" )? As far as I understand, now we will need to have 2
translations, first for "Height" and
Just few examples (expanding jp's answer):
having a schematic symbol, being virtual, having 3d model are not
related (you can have any combination of them). As examples:
First: a virtual footprint that has a schematic symbol (the answer to
your main question).
Edge connector: schematic symbol
ything I would say to break down the statistics based on via type.
On Sun, Jul 21, 2019 at 1:55 PM Dino Ghilardi <mailto:dino.ghila...@ieee.org>> wrote:
I just tried the board statistics dialog and looks good, I like it.
A thing I'd like to have to make it better is adding t
I just tried the board statistics dialog and looks good, I like it.
A thing I'd like to have to make it better is adding the number of vias
to the statistics: Since making every hole in the pcb costs time,
manufacturers calculate the price of the PCB using also that number.
Also the option to
Hi,
"GCC has full support for the previous revision of the C++ standard,
which was published in 2014." [gcc official documentation]
gcc documentation also reports that gcc6 supports c++14, excluding the
"Clarifying memory allocation" language feature.
If you are interested in it, a list of
I see that too (linux - Debian 9.9), same error got from line 455.
I tried also a "git clean -fx" and a clean build to see if it was from
an auto-generated file, but the problem persists, also using cmake to
re-generate everygthing.
--
/home/dinogh
On 11/07/19 18:16, easyw wrote:
On 07/11/2019 5:17 PM, Jeff Young wrote:
Here’s a footprint I drew recently which was made much harder by
Kicad’s focus on arc centre points:
This is exactly an example that should be done in a mechanical CAD and
imported later in KiCAD (i.e. as DXF).
Co
On 11/07/19 14:42, easyw wrote:>
> On 07/11/2019 1:21 PM, Dino Ghilardi wrote:
>> On 11/07/19 12:26, easyw wrote:
>> then your fashion design should use a proper CAD to design the board,
>> and the EDGE should then imported inside KiCAD i.e. from a svg or a
>> dxf
On 11/07/19 12:26, easyw wrote:
On 07/11/2019 12:05 PM, Dino Ghilardi wrote:
My two cents...
Unfortunatly some times the centers are anchors of the board, other
times they are not: when the external case is designed by a "fashon
designer" and you have to put your electronics i
On 07/10/2019 10:52 PM, Eeli Kaikkonen wrote:> For what it's worth, in
normal graphical arcs (especially in edge cuts) the
two endpoints (or start and end) are usually important, the centerpoint
isn't.
This is not true. Generally for mechanical concerns, you should start
exactly from the ce
As an alternative to the .99 numbering (that should work well until 5.98
stable version is reached (! :-) ) ) also think about the linux kernel
versioning number scheme: even subversion number means stable release. Odd
subversion number means experimental/development branch. At every release
of th
commit 4852c91b423abf1e3e745f9d17ad56c92d5445b8
does not compile for me on Linux, even re-generating config files with
cmake.
Does anybody else have the same issue?
The missing definitions seems to be in pcb_lexer.h, but this is not
included in pcb-parser.cpp. Should it?
When "make -j7" f
Just a thought (may be a little off-topic):
Since old pcbnew versions will not be able to open files in new format,
there should be a way to export a pcb in the "old/stable" format, so
that when testing latest development version of pcbnew on an old board
(and saving it) can be undone without
This mail just to "close" the issue.
This morning I just Tested commit 589a37bfe8c773d621b6dae9a0f3347babaf1ba1
and now it works correclty for me (no more segfaults).
Cheers,
Dino.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to
Hi,
In today's version I experience a segfault anytime a paste operation is
aborted using the "esc" key.
How to reproduce the behaviour.
-Create a new schematic
-Add a GND symbol
-Copy it with ctrl-c
-Paste it with ctrl-v, without confirming with click or enter
-ESC key to abort,
then an ass
...I forgot to paste version information... here they are
--
Application: kicad
Version: (5.1.0-512-g5f4a6e33a), debug build
Libraries:
wxWidgets 3.0.2
libcurl/7.52.1 OpenSSL/1.0.2r zlib/1.2.8 libidn2/0.16 libpsl/0.17.0
(+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1
Hello everybody, I've seen a "fast fix" an eemodern, so...
The "return" hotkey for "left-click" is not working for me on
2d2b5f3e1915a270f2a51eb342f761df8b8a0122 doing a "paste" function.
Reproducing it:
-Select a block
-ctrl-c for copy
-ctrl-v for paste
Small patch to save and reload print configurations. Adds "Save config"
and "Load Config" buttons in the print dialog.
Just the same patch I sent long ago, but in a single file.
Useful when is needed to create documents with multiple pages that merge
informations from different layers, so you ca
Hello JP,
'interleaved' to the original text my comments.
Il 23/12/2016 08:56, jp charras ha scritto:
Le 23/12/2016 à 00:30, Dino Ghilardi a écrit :
...
Yes, the undo/redo on multiple sheets is very tricky, mainly because usually
you are not expecting
this command made in a g
Il 22/12/2016 13:03, Nox ha scritto:
Hello Dino,
Afaik the undo/redo system of Eeschema does not support "batching" of
changes natively. Generally speaking the undo/redo system of Eeschema
could need some attention but I do not know how worthwhile it is
considering the announced refac. There
Il 20/12/2016 09:59, jp charras ha scritto:
Le 08/11/2016 à 01:29, Dino Ghilardi a écrit :
Hello everyone,
Thanks for the comments on this tool and the video.
...
Hi Dino,
Have you a more recent version of your tool, including a few enhancements you
have listed?
This tool is very
the code (aka re-read all
and check code style policy) and create a patch to send to the mailing
list, so I'll wait to hear if it is a good idea to go on developing this
tool or not.
Cheers,
Dino Ghilardi.
___
Mailing list: https
Hi everybody,
Attached there is a patch to add the save function for the configuration
of the print dialog.
Often I need to generate prints from combined layers to have documents
for production and selecting every time the right combination of layers
and features is error prone and cumbersome,
Hi everybody,
In the last few days I used kicad and i noticed that It was useful to me
to have 'hide all layers' and a 'show all layers' in the pcbnew layer
toolbar popup.
I'm attaching the (small) patch, so that (if useful) can be used.
Bye,
Dino.
>From ec31006cf8714f65aa939e33c2ebd5b68dbc8
Hello,
Attached there is a couple of new possible example scripts in python.
They change the reference designator text size of all the refdes in the
open pcb. The scripts are:
simpleSetAllReferenceSizes.py: simple text only version (as a
simple example)
setAllReferenceSizes.py : uses wx
Hi, I saw that my skins are not usable with version 0.7.
If you like I can update them:
- In wich format are they needed?
- What have I to modify?
- Is there an how-to to prepeare new skins?
Bye, Dino Ghilardi.
[EMAIL PROTECTED]
___
Wormux-dev mailing
48 matches
Mail list logo
