g like GetMinimalVersionNumber()) to all
>>>> board items (tracks, texts
>>>> footprints, pads...), each item can return the needed minimal version to
>>>> be read in file.
>>>> Currently they could return 4, but for a
Patch committed in rev 6685. Thank you.
On Sun, Apr 10, 2016 at 10:39:26AM +1000, Cirilo Bernardo wrote:
> The attached patch fixes a segfault due to a race condition.
> If a user starts eeschema with an empty sheet and clicks
> the 'cvpcb' button, memory is corrupted and the program
> segfaults.
gt;>> If a method is added (something like GetMinimalVersionNumber()) to all
>>> board items (tracks, texts
>>> footprints, pads...), each item can return the needed minimal version to be
>>> read in file.
>>> Currently they could return 4, but
I just fixed three of them. If there are others, I didn't see them, so please
point them out to me.
On Sat, Apr 09, 2016 at 07:47:28PM -0400, Wayne Stambaugh wrote:
> Great! Thanks for fixing this. It's been a long time coming.
>
> On 4/9/2016 4:20 PM, Chris Pavlina wrote:
> >
to all board
>> items (tracks, texts
>> footprints, pads...), each item can return the needed minimal version to be
>> read in file.
>> Currently they could return 4, but for a pad, if its type is rounded rect it
>> will return 20160410,
>> and therefore its
ly they could return 4, but for a pad, if its type is rounded rect it
> will return 20160410,
> and therefore its footprint parent returns 20160410 (or 4 if no rounded rect
> pad is found)
>
> Before writing the file, just run BOARD::GetMinimalVer
return 4, but for a pad, if its type is rounded rect it
will return 20160410,
and therefore its footprint parent returns 20160410 (or 4 if no rounded rect
pad is found)
Before writing the file, just run BOARD::GetMinimalVersionNumber() to know the
actual needed version.
--
Jean-Pierr
You seem to be confusing backward and forward compatibility...
no
just read my comments from the first mail ...
I always ask to have the ability to save a board with a back release nbr
from the new release, if there is not new features on it
... anyway just do what you care
cheers
On
On Sun, Apr 10, 2016 at 03:30:15PM +0200, easyw wrote:
> >From what I've seen of the forums, the users complain about _everything_, I
> >don't think it's necessarily our job to minimize complaints. ;)
> so this is as I thought... users point of view don't count so much
>
> >4022 is _old_. If
From what I've seen of the forums, the users complain about _everything_, I
don't think it's necessarily our job to minimize complaints. ;)
so this is as I thought... users point of view don't count so much
4022 is _old_. If you're still using it, upgrade.
I was pointing out the case of
Le 10/04/2016 02:49, Chris Pavlina a écrit :
> Possible to implement, of course, but that could get rather messy as the
> parser
> has to be taught to ignore things it doesn't recognize, which is not exactly
> easy given the context-sensitive nature of our kinda-sorta-pseudo-parser
>
the problem is you are dealing with potentially very close tolerance.
and numerous other issues that if htere is a compatibility possibility
we will probably get people saying that compatibility breaks their
design. There comes a point where it just has to be dealt with, a save
with compatibility
>From what I've seen of the forums, the users complain about _everything_, I
don't think it's necessarily our job to minimize complaints. ;)
4022 is _old_. If you're still using it, upgrade. If you're still running
Ubuntu 320BC.06 and it doesn't run, upgrade that too. :P
On Sun, Apr 10, 2016 at
I don't really see much reason to care if 4.0 can emit board files 4022 can
read.
4022 was considered STABLE for very long time, many users didn't want to
move from there for long time...
Now the 4.0 is the 'new stable' release and a lot of users will not
switch to the new for long time (till
The upgrade from 4022 to 4.0 wasn't as smooth as it could have been, no. But
tbh I don't really see much reason to care if 4.0 can emit board files 4022 can
read. Upgrade to 4.0. It's KiCad, not Altium, it's free. You can upgrade.
Now, if 4022 emits files 4.0 can't read, that's a separate
This gets filed under "things said by people who haven't seen what'd be necessary to
implement that" ;)
This gets filed under "things said by people who cares about what user's
need in a real production world"
If you don't care about what happened with the 4022 vs new stable for
users,
This gets filed under "things said by people who haven't seen what'd be
necessary to implement that" ;)
On Sun, Apr 10, 2016 at 10:23:22AM +0200, easyw wrote:
> I think there should be an option to export a new board version to previous
> version, eventually warning on what could be lost if the
I think there should be an option to export a new board version to
previous version, eventually warning on what could be lost if the file
contains some new features...
that is a standard feature in most sw, to allow a better collaborative
environment
Maurice
On 10/04/2016 02.49, Chris
18 matches
Mail list logo
