kicad-developers team mailing list archive

[Jon Evans <jon@xxxxxxxxxxxxx>]

Yeah I also agree that it should be basically a dialog of eeschema rather
than a separate program, so I guess it makes sense to write changes
immediately to the in-memory schematic, and mark it as unsaved for the user
to consciously hit the save button later if desired.

-Jon

On Tue, Mar 20, 2018 at 1:52 PM, Russell Oliver <roliver8143@xxxxxxxxx>
wrote:

> I second Bernhard's comments.
> I think it shouldn't seem like a separate program, just another dialog of
> eeschema that takes the what you see is what you get approach.
> As long as the footprint references are valid the schematic should be
> updated when the dialog is closed, and marked modified if there was a
> change.
> Saving the schematic to file is then done through eeschema proper.
>
> Russell
>
> On Wed, 21 Mar 2018 04:40 Bernhard Stegmaier, <stegmaier@xxxxxxxxxxxxx>
> wrote:
>
>> Just my 2 cents…
>> I would immediately write back any change in cvpcb to schematic.
>> I never understood why I have to hit the button to do that.
>> There is no PCB preview or something like that in cvpcb, so I have to
>> apply all changes anyway to check them directly in the PCB.
>> Then, keep the button and save schematic with it.
>>
>>
>> Regards,
>> Bernhard
>>
>> On 20. Mar 2018, at 18:28, Jon Evans <jon@xxxxxxxxxxxxx> wrote:
>>
>> Why don't you like the idea of saving the schematic when you hit the save
>> button? That seems like a reasonable expected behavior to me at least.
>>
>> (I dislike nag dialogs especially when they seem to have no purpose)
>>
>> -Jon
>>
>> On Tue, Mar 20, 2018 at 1:26 PM, Jeff Young <jeff@xxxxxxxxx> wrote:
>>
>>> CvPcb has a Save command (complete with disk icon).  Only it doesn’t do
>>> that.  (It simply writes the changes back to eeschema.)
>>>
>>> If it were a dialog, I’d say that’s not good.  But this is CvPcb, where
>>> you could easily spend an hour making associations (hitting save every few
>>> minutes), only to have your machine and/or Kicad go down with all your
>>> changes.  That’s borderline horrific.
>>>
>>> I don’t like the idea of blind-saving the eeschema document, but I think
>>> that would be better than what we have now.
>>>
>>> Another idea would be to trigger an auto-save for each CvPcb save.  It’s
>>> not ideal because the user may think that there aren’t any changes in their
>>> eeschema file and therefore ignore the auto-save warning when restarting.
>>>
>>> Yet another idea would be to foist the decision on the user with a “Save
>>> your schematic?” dialog every time you save in CvPcb.  That’s pretty hard
>>> to love, but with Orson’s new KIDIALOG we could at least have a “don’t ask
>>> me again” checkbox.  Maybe that’s not so bad….
>>>
>>> Thoughts?
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>