On Sun, Aug 17, 2014 at 12:05:41PM +, Mário Luzeiro wrote:
Is that expected? I mean, should I continue build with wxwidgets 3.0 or
revert it back?
AFAIK 2.8 is no longer supported since the new modular stuff doesn't
work correctly with it.
--
Lorenzo Marcantonio
Logos Srl
Le 17/08/2014 00:45, Mário Luzeiro a écrit :
Hi all,
I implemented some new (old wishes) improvements to 3D-Viewer.
Also, the overall render was improved.
All changes related with 3D-Viewer:
- Remove HightQualityMode (now is remove holes option)
+ Render smooth option
+ Render shadow
I am interested in working on the model cache system (I was the one who
originally proposed it) but won't have the time to work on it for
another week or so.
If anyone else is interested in getting started in the meantime please
coordinate with me so we don't duplicate efforts, if not I'll let
*Dear KiCad Developers,Greetings from Oscad Team, IIT Bombay!In
continuation to the earlier discussions, we would like to propose the
following roadmap:Integration of ngspice to KiCadCurrently, Oscad uses
KiCad for schematic creation and uses ngspice for simulation. Ngspice has
its inbuilt
Hi Andrew,
I will not be available currently to directly support you, but after some
recent analyse of 3DViewer and how it works regarding the redraws I have some
suggestions and they are not model cache related.
Background:
Right now, after 3d viewer open and load everything, my main concern
2014-08-18 12:15 GMT+02:00 Mário Luzeiro mrluze...@ua.pt:
[...]
btw.. I have an idea that the other $$ EDA $$ software $$ packages (e.g:
altium) are able to view in real time the 3D board while you are editing the
traces on pcb board... that is a big goal to archive ;)
Kicad is (or has)
Nick, you (may be) are correct. I have that idea too.
But what I mean is that right now and special with complex boards it will take
too much time to rendering everything again (re calculating the board
polygons.. re-render all model positions... etc). So it is not real time (for
me).
Hello Dick
I see a bug in your commit 5072 (also present in latest commit 5079).
In that commit; when opening a schematic, then all connections are
showed as not connected (with the square green box around the end
nodes). When drawing a new wire they all look connected again. See the
attached
Le 18/08/2014 01:04, Dick Hollenbeck a écrit :
Patch solved the issue, seemed to work like a charm... But induced another
issue. Step to
reproduce :
1 - open kicad, then open eeschema and pcbnew
2 - in pcbnew, open the module properties dialog on any part you want.
3 - go back to eeschema,
Good news !
thanks Dick !
but where is that 5089 version ? I just ran the install script and it
updated to 5081. May be it was 5079 ?
Yes.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to :
On 08/18/2014 05:37 AM, Nick Østergaard wrote:
Hello Dick
I see a bug in your commit 5072 (also present in latest commit 5079).
In that commit; when opening a schematic, then all connections are
showed as not connected (with the square green box around the end
nodes). When drawing a new
2014-08-18 19:39 GMT+02:00 Dick Hollenbeck d...@softplc.com:
On 08/18/2014 05:37 AM, Nick Østergaard wrote:
Hello Dick
I see a bug in your commit 5072 (also present in latest commit 5079).
In that commit; when opening a schematic, then all connections are
showed as not connected (with the
I found that if I have multiple libraries with same component names (notable
ex: R, C, INDUCTOR .. ) I cannot select another component other than the one
already cached (?). I mean, if I select a R from another library it will load
the same R as already loaded in the schematic.
I am not sure if
On 8/18/2014 4:30 PM, Mário Luzeiro wrote:
I found that if I have multiple libraries with same component names (notable
ex: R, C, INDUCTOR .. ) I cannot select another component other than the one
already cached (?). I mean, if I select a R from another library it will load
the same R as
On 08/18/2014 03:30 PM, Mário Luzeiro wrote:
I found that if I have multiple libraries with same component names (notable
ex: R, C, INDUCTOR .. ) I cannot select another component other than the one
already cached (?). I mean, if I select a R from another library it will load
the same R as
The order of parts search is given by the order of library names in the *.pro
file.
Here in my project, you see the first two are mine, followed by the standard
ones.
One is project specific and the other is cross project:
If you change this order, by dialog or text editor, you will get
On 08/18/2014 03:36 PM, Wayne Stambaugh wrote:
On 8/18/2014 4:30 PM, Mário Luzeiro wrote:
I found that if I have multiple libraries with same component names (notable
ex: R, C, INDUCTOR .. ) I cannot select another component other than the one
already cached (?). I mean, if I select a R from
On 08/18/2014 04:03 PM, Dick Hollenbeck wrote:
On 08/18/2014 03:36 PM, Wayne Stambaugh wrote:
On 8/18/2014 4:30 PM, Mário Luzeiro wrote:
I found that if I have multiple libraries with same component names
(notable ex: R, C, INDUCTOR .. ) I cannot select another component other
than the one
Hi Dick,
Thanks for your explanations.
This is fun, considering the years I am using kicad and only now find this
situation :)
I was right now checking the project files looking for the libraries and I have
this scenario:
main_project.pro - [eeschema/libraries] .. list of libraries
On 08/18/2014 04:26 PM, Mário Luzeiro wrote:
Hi Dick,
Thanks for your explanations.
This is fun, considering the years I am using kicad and only now find this
situation :)
I was right now checking the project files looking for the libraries and I
have this scenario:
main_project.pro
I will do the workaround reordering of my libraries.. not a problem for me
now that I know how it works..
I think the sort() call has to go, so I now think you discovered something.
Should have a fix in minutes.
When the foundations get simpler, so do the algorithms.
Dick
On 16 August 2014 17:44, Wayne Stambaugh stambau...@verizon.net wrote:
One of the tasks that I have committed to working on in the KiCad road
map is to clean up the current mess we have created by allowing
dependency libraries to be built as part of the KiCad source build. The
only exception
On 14 August 2014 23:55, Derek Kozel derek.ko...@gmail.com wrote:
Hello!
First of all thank you to everyone who has contributed to getting KiCad to
where it is now. I've made several boards with it and hope to make many
more. I'm a recent EE/CS graduate with experience working on medium sized
On 4 August 2014 17:05, Dick Hollenbeck d...@softplc.com wrote:
I pushed an early branch of this work to milestoneB.
See the commit log for some of the details.
The shared_ptr turned out to be a can of worms. No, several cans of worms,
all stacked
like a 2 miles of dominos.
So I used a
Dear Oscad Developers,
Your work sounds interesting. I have a few questions about the current
state of your code:
1) I've been working under the assumption that you were interested in
merging your work into KiCad to provide an integrated simulator solution
but it almost sounds like you are
On 8/18/2014 6:45 PM, Brian Sidebotham wrote:
On 16 August 2014 17:44, Wayne Stambaugh stambau...@verizon.net wrote:
One of the tasks that I have committed to working on in the KiCad road
map is to clean up the current mess we have created by allowing
dependency libraries to be built as part
26 matches
Mail list logo
