On 02/09/2018 08:00 AM, Marco Ciampa wrote:
> On Fri, Feb 09, 2018 at 07:34:41AM +0100, Carsten Schoenert wrote:
>> Am 09.02.2018 um 01:54 schrieb Wayne Stambaugh:
>>> For the libs, docs, and translations, I'm ok if we hold off tagging
>>> until the stable release if that works for you.
>>
>>
On Fri, Feb 09, 2018 at 07:34:41AM +0100, Carsten Schoenert wrote:
> Am 09.02.2018 um 01:54 schrieb Wayne Stambaugh:
> > For the libs, docs, and translations, I'm ok if we hold off tagging
> > until the stable release if that works for you.
>
> Correct as this needs to be done by the respective
Am 09.02.2018 um 01:35 schrieb Jeff Young:
> Ping.
>
> Any thoughts on patching wxWidgets for other platforms?
If you are talking about other Linux platforms then please do this in a
way the user hasn't to deal with changes to system folders, this isn't
really possible nor usable on systems
Am 09.02.2018 um 01:54 schrieb Wayne Stambaugh:
>> If you want to tag rc1 this weekend, should we tag the libs as well?
Absolutely! Don't make the life of distributions and packagers more
complicated than needed.
There was a interesting talk on FOSDEM about how to make releases right
(in terms
On 02/08/2018 07:47 PM, Rene Pöschl wrote:
On 09/02/18 01:28, Wayne Stambaugh wrote:
Assuming this can be completed in a reasonable amount of time and it is
consistent then I'm fine with this going into v5. This is just cosmetic
and isn't going to break anything. I've got a few more patches
On 09/02/18 01:28, Wayne Stambaugh wrote:
Assuming this can be completed in a reasonable amount of time and it is
consistent then I'm fine with this going into v5. This is just cosmetic
and isn't going to break anything. I've got a few more patches to
review and some work of my own to finish
Ping.Any thoughts on patching wxWidgets for other platforms?On 6 Feb 2018, at 14:08, Jeff Young wrote:I accidentally dropped the dev list off the last few replies. They included an update which fixed the issue Seth hypothesised.But I’m updating it one more time because, well, I
Assuming this can be completed in a reasonable amount of time and it is
consistent then I'm fine with this going into v5. This is just cosmetic
and isn't going to break anything. I've got a few more patches to
review and some work of my own to finish up over the weekend so I would
like to
On 08/02/18 22:47, Steven A. Falco wrote:
> On 02/08/2018 04:28 PM, Tomasz Wlostowski wrote:
>> On 08/02/18 21:15, Steven A. Falco wrote:
>>> I continue to have problems performing a zone fill with the latest kicad 5
>>> builds. A copy of the project that is causing me trouble is here:
Thanks.
On 02/08/2018 04:28 PM, Tomasz Wlostowski wrote:
> On 08/02/18 21:15, Steven A. Falco wrote:
>> I continue to have problems performing a zone fill with the latest kicad 5
>> builds. A copy of the project that is causing me trouble is here:
>>
>>
On 08/02/18 21:15, Steven A. Falco wrote:
> I continue to have problems performing a zone fill with the latest kicad 5
> builds. A copy of the project that is causing me trouble is here:
>
> https://www.dropbox.com/sh/lw7lhg7jyigvyi7/AAB0ALAWmYS2LmOlw7-spqP6a?dl=0
Steve,
3 quick questions:
-
On 2018-02-08 07:02 AM, kristoffer Ödmark wrote:
for example, disbling rendering of front footprints disables all the F.Silk,
F.Fab, adhesive and many more.
Disabling the rendering of Text on the front only disables text belonging to
a footprint, no other. Basically the Render tab does not do
I think it has been mentioned before about potentially creating user
defined visibility settings that could be added to the layer manager
context menu. I'm guessing that we would have to rework some of the
underlying code to make this possible. It's definitely something to
keep in mind for
I continue to have problems performing a zone fill with the latest kicad 5
builds. A copy of the project that is causing me trouble is here:
https://www.dropbox.com/sh/lw7lhg7jyigvyi7/AAB0ALAWmYS2LmOlw7-spqP6a?dl=0
I can reproduce the problem on both a Windows 10 VM, running
Tom,
Did answering your question resolve the questions you asked below? I
apologize for being brief but I'm really busy trying to get a new stable
release of KiCad out so please be patient.
Wayne
On 2/4/2018 11:48 AM, Tom Cook wrote:
> Hello,
>
> I'm developing a small Python application for
KiCad uses the system default association when opening a text or pdf
file from within KiCad unless you explicitly change it. I would think
most users are aware that the system already has a default app
associated with text and pdf files. The KiCad option is to use
something other than the system
Do all our platforms have an OS default? If so, I agree: nuke the setting
entirely.
> On 8 Feb 2018, at 17:42, Andrey Kuznetsov wrote:
>
> We agree, good job, 24->0 words!
> No need to specify something that's already been set system wide.
>
> On Thu, Feb 8, 2018 at 8:06
We agree, good job, 24->0 words!
No need to specify something that's already been set system wide.
On Thu, Feb 8, 2018 at 8:06 AM, Andy Peters wrote:
>
> On Feb 8, 2018, at 3:42 AM, Jeff Young wrote:
>
> > … or "Set default text editor and PDF viewer programs
Hi Thomas-
That makes sense. The REGEX fails because you haven't installed
OpenCascade. You've only built it. When you install it,
Standard_Version.hxx will be correct and the REGEX will match. In the
build directory, it only includes the header from the source directory.
I suspect (but
I’ve attached the output from when I try to configure with the original file.
The version checking didn’t work for 7.1 for me either. It should be noted, that
I built OpenCascade from source, and I’ve tried to manually change it to point
to the Standard_Version header, but it still doesn’t parse
Hi Thomas-
I will add this library to the include. Odd that it wasn't required on
Linux. Can you send me your CMakeOutput.log? The version checking is
pretty important and those files don't change, so I'd like to track down
why it would work for 7.1 but not for 7.2.
-S
2018-02-08 7:29
> On Feb 8, 2018, at 3:15 AM, Andrey Kuznetsov wrote:
>
> Wow, that sentence is unnecessarily long.
>
> By rephrasing, you can cut that text in half. Also, why is text editor and
> PDF viewer in the same context? Default text editor and default PDF viewer do
> not open
> On Feb 8, 2018, at 3:42 AM, Jeff Young wrote:
>
> > … or "Set default text editor and PDF viewer programs to open files from
> > KiCad”
>
> +1
One could interpret “open files from KiCad” as being “Open files created by
KiCad.”
The point I was trying to make, and perhaps
As you noticed, one can only define simple layer visibility dependencies
in GAL using SetRequired() method. Effectively, you can quickly disable
a whole layer when another is invisible, but it does not handle well
cases of e.g. texts whose visibility should depend both on the layer and
the parent
Andrzej,
I merged your patch into the development branch. Thank you for your
contribution to KiCad.
Cheers,
Wayne
On 1/15/2018 9:09 AM, Andrzej Wolski wrote:
> LAYER_VIAS_NETNAMES color was not initialized which resulted in black
> text, not visible in outline mode.
>
> This patch sets color
I started investigating this some more, there is much more rendering
problems here.
for example, disbling rendering of front footprints disables all the
F.Silk, F.Fab, adhesive and many more.
Disabling the rendering of Text on the front only disables text
belonging to a footprint, no other.
There is still one problem to be solved here: worksheet layout is not
saved in schematic file, so the default worksheet is restored when an
imported project is saved and reloaded.
I have nothing against the patch, it gives a nicer first impression.
Cheers,
Orson
On 02/07/2018 04:44 PM, Wayne
Thanks Jeff,
That's 35->13 (2.7x) word reduction or 24->8 (3x) reduction for the less
explicit sentence.
Description text shouldn't be longer than 12-18 words, if it is it needs
rephrasing and/or help reference tag.
On Thu, Feb 8, 2018 at 2:42 AM, Jeff Young wrote:
> > … or
> … or "Set default text editor and PDF viewer programs to open files from
> KiCad”
+1
> On 8 Feb 2018, at 10:15, Andrey Kuznetsov wrote:
>
> Wow, that sentence is unnecessarily long.
>
> By rephrasing, you can cut that text in half. Also, why is text editor and
> PDF
Apparently you got it to work, cool! What was the actual problem? Do you
use ngspice v26 or v27? Would you share the patch?
Regards,
Orson
On 02/08/2018 11:19 AM, ludovic léau-mercier wrote:
> I work on. First result in attachment.
>
>
> On 08/02/2018 10:07, Maciej Sumiński wrote:
>> Hi
I work on. First result in attachment.
On 08/02/2018 10:07, Maciej Sumiński wrote:
Hi Ludovic,
If I recall correctly, when you run an analysis different than
transient, ngspice will not return any data when you ask for currents.
There is also another related line:
void
Wow, that sentence is unnecessarily long.
By rephrasing, you can cut that text in half. Also, why is text editor and
PDF viewer in the same context? Default text editor and default PDF viewer
do not open the same files, is this a context for a Group where those 2 are
defined, weird...
Telling
Attached is a minimal patch that differs the dialog title.
- Kristoffer
On 2018-02-05 13:25, Marco Ciampa wrote:
On Mon, Feb 05, 2018 at 01:10:08PM +0100, kristoffer Ödmark wrote:
Hey!
I just spent some time trying to "debug" a library non-issue with a EE
switching from Altium for a test. He
Hi Ludovic,
If I recall correctly, when you run an analysis different than
transient, ngspice will not return any data when you ask for currents.
There is also another related line:
void NETLIST_EXPORTER_PSPICE_SIM::writeDirectives( OUTPUTFORMATTER*
aFormatter, unsigned aCtl ) const
{
// Add
Am 08.02.2018 um 09:29 schrieb Nick Østergaard:
> Please keep in mind that experienced users probably don't really read
> the full text of the various information strings as they have seen this
> for several times already.
> But the not well experienced or new users have problems
Hi all,
i try to create a patch to adding several improvment of eeshema simulation.
My first goal is to draw BJT caracteristics (like
https://www.st-andrews.ac.uk/~www_pa/Scots_Guide/info/comp/active/BiPolar/IcVce.gif)
with a simplest circuit in attachment.
I had beginning to work on this
2018-02-08 <20%2018%2002%2008> 6:53 GMT+01:00 Carsten Schoenert <
c.schoen...@t-online.de>:
> Hi,
>
> Am 08.02.2018 um 01:06 schrieb Nick Østergaard:
> > I also thinks that adding "by Kicad" does not add any information. It
> > only complicates the already long description.
>
> I disagree here
...and for some reason antialiasing stays enabled anyway. I retract the
question.
Cheers,
Orson
On 02/08/2018 09:01 AM, Maciej Sumiński wrote:
> One more question, I have just realized that I disabled antialiasing
> when USE_WX_GRAPHICS_CONTEXT is enabled. Is that fine for macOS or
> eeschema
One more question, I have just realized that I disabled antialiasing
when USE_WX_GRAPHICS_CONTEXT is enabled. Is that fine for macOS or
eeschema runs fast enough, so antialiasing is preferred?
Cheers,
Orson
On 02/07/2018 06:36 PM, Bernhard Stegmaier wrote:
> … yes, no good.
> It seems to be OK
39 matches
Mail list logo