Hi Wayne
On 19/04/17 03:34, Wayne Stambaugh
wrote:
Hey David,
On 4/18/2017 3:32 PM, David Godfrey wrote:
It would also break re-usability. I I have
a schematic file that
represents an instrument amp, and use it as a sheet
As already mentioned by jp several issues can occur with that approach.
E.G. if following operations on one sheet "desyncs" the stacks. But
maybe it is really an alternative to use a mixed approach with a "pop up
dialog" giving the option to either only revert the active vs all sheets
and ask
What about storing undo information per sheet as done now, but allow
optional grouping of such a operation across sheets.
When KiCad detects the user want's to undo a operation which affects
multiple sheets, he get's a message to chose about reverting the change
only in the the current sheet / or
Of course it is a valid solution but is it really the most convenient to
break the undo/redo stack for a operation like annotiating? As already
mentioned there are "text" editors (e.g. visual studio) which handle a
replacement in multiple files differently (e.g. try to undo/redo on all
On 4/18/2017 3:35 PM, Jon Evans wrote:
> Hi David,
>
> This is why other EDA tools have a clear differentiation between
> hierarchical blocks (what you are talking about) and multi-sheet
> schematics (what I am talking about). The fact that KiCad mixes the two
> makes it difficult to implement
On 4/18/2017 3:37 PM, Tomasz Wlostowski wrote:
> On 18.04.2017 21:32, David Godfrey wrote:
>
>>> This would break complex hierarchies where a file is referenced in more
>>> than one sheet. Using separate files for each sheet actually makes
>>> designs less reusable in complex hierarchies. It
Hey David,
On 4/18/2017 3:32 PM, David Godfrey wrote:
> Hi Jon
>
>
> On 18/04/17 21:27, Wayne Stambaugh wrote:
>> On 4/18/2017 9:03 AM, Tomasz Wlostowski wrote:
>>> On 18.04.2017 14:55, Jon Evans wrote:
(branched from the component table viewer thread)
In my opinion, a schematic
On 18.04.2017 21:32, David Godfrey wrote:
>> This would break complex hierarchies where a file is referenced in more
>> than one sheet. Using separate files for each sheet actually makes
>> designs less reusable in complex hierarchies. It doesn't make sense to
>> save the same file multiple
Hi David,
This is why other EDA tools have a clear differentiation between
hierarchical blocks (what you are talking about) and multi-sheet schematics
(what I am talking about). The fact that KiCad mixes the two makes it
difficult to implement some features in a way similar to commercial EDA
On 4/18/2017 9:03 AM, Tomasz Wlostowski wrote:
> On 18.04.2017 14:55, Jon Evans wrote:
>> (branched from the component table viewer thread)
>>
>> In my opinion, a schematic with multiple sheets is not like a text
>> editor with multiple documents. The schematic editor is working on a
>> single
On 4/18/2017 8:55 AM, Jon Evans wrote:
> (branched from the component table viewer thread)
>
> In my opinion, a schematic with multiple sheets is not like a text
> editor with multiple documents. The schematic editor is working on a
> single project, and it should be way more common to apply
On 18.04.2017 14:55, Jon Evans wrote:
> (branched from the component table viewer thread)
>
> In my opinion, a schematic with multiple sheets is not like a text
> editor with multiple documents. The schematic editor is working on a
> single project, and it should be way more common to apply
Hi,
On 18.04.2017 14:55, Jon Evans wrote:
> In my opinion, a schematic with multiple sheets is not like a text
> editor with multiple documents. The schematic editor is working on a
> single project, and it should be way more common to apply operations
> (that might want to be undone) to all
(branched from the component table viewer thread)
In my opinion, a schematic with multiple sheets is not like a text editor
with multiple documents. The schematic editor is working on a single
project, and it should be way more common to apply operations (that might
want to be undone) to all
14 matches
Mail list logo
