thank you all for this fruitful discussion
Am 04.05.24 um 16:48 schrieb Jeff Young:
I'll work on the quick version as a start
:thumbsup:
--
You received this message because you are subscribed to the Google Groups "KiCad
Developers" group.
To unsubscribe from this group and stop
> I'll work on the quick version as a start
:thumbsup:
--
You received this message because you are subscribed to the Google Groups
"KiCad Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to devlist+unsubscr...@kicad.org.
To view this
I'll work on the quick version as a start
On Sat, May 4, 2024 at 10:36 AM Wayne Stambaugh wrote:
>
> Until we have a more elegant solution such as Jon's info bar suggestion,
> we could do something similar for libraries by using an option in the
> library table entry.
>
> On 5/4/24 10:30 AM,
Until we have a more elegant solution such as Jon's info bar suggestion,
we could do something similar for libraries by using an option in the
library table entry.
On 5/4/24 10:30 AM, 'Seth Hillbrand' via KiCad Developers wrote:
For importing boards, we could
1) Add a checkbox at the bottom
I like it. Works for me.
[image: KiCad Services Corporation Logo]
Seth Hillbrand
*Lead Developer*
+1-530-302-5483
Long Beach, CA
www.kipro-pcb.comi...@kipro-pcb.com
On Sat, May 4, 2024 at 7:34 AM Jon Evans wrote:
> I think a variant of (2) where we move the messages to a custom dialog
I think a variant of (2) where we move the messages to a custom dialog and
show an info at with a button to open the dialog would be faster (adding
new AUI is going to be more complex IMO)
(1) makes sense to me for 8.x
On Sat, May 4, 2024, 10:30 'Seth Hillbrand' via KiCad Developers <
For importing boards, we could
1) Add a checkbox at the bottom of the import non-KiCad dialog that says
"Show import errors"
and/or
2) Move the error reporter to a docked AUI window so that it doesn't
interrupt the workflow
Seth
[image: KiCad Services Corporation Logo]
Seth Hillbrand
*Lead
Following up, I think it's important to understand the places the importer
is used for my team (and probably others who use a mix of tools)
The importers are rarely used as a "one shot" tool to convert a design
permanently from a different CAD tool to KiCad. Instead, we use the
importers
I agree that the information should be exposed somewhere. But I think
interrupting the load process with a dialog is a nag. It gets in the way of
using KiCad as an efficient way to view files designed in other programs.
On Sat, May 4, 2024, 09:52 Jeff Young wrote:
> I don’t agree. A nag dialog
For board imports, I agree with the desire to know what is missing. The
current report is not helpful in this regard because it tells you that
something is missing without enough context to do anything about it.
For library imports, this needs something completely different. Especially
as we
I don’t agree. A nag dialog would be something that told you we don’t have an
editing feature that Altium supports, not that we can’t express the same end
result as we found in the Altium file.
There are certainly border-line cases. Complaining about not being able to
import a datum
> The only place we disagree is what to do in the meantime for schematics and
> boards.
Using wxLog to pop up dialogs reporting that KiCad does not support
some feature of some other EDA tool is inappropriate in my opinion.
It goes against the KiCad guideline of not showing nag dialogs. I
don't
We do report context info (at least line number and offset) in some of the
other importers.
I agree that the system could be improved.
And I agree that we have to do something about the library importing.
The only place we disagree is what to do in the meantime for schematics and
boards.
Jeff,
In both cases I disagree that the current warning system should
appear. The warning system we have today is really not that helpful,
and I don't want to bring it back the same way for boards or for
libraries.
The advanced_config option was something Seth and I discussed as a
simple stopgap
Presumably we can tell the difference (in the code) between a schematic or
layout import and a library import?
It would seem to me like a schematic or layout import should show the warnings
(even without an advanced setting or the like).
Personally I also think the library importer should show
Hi,
I recently started a discussion with @Jon Evans in my MR
https://gitlab.com/kicad/code/kicad/-/merge_requests/1935 regarding the
visibility of Altium importer warning & errors for not yet supported
schematic and layout features.
Since commit
16 matches
Mail list logo
