On Sat, Nov 19, 2016 at 12:20 AM, Joerg Wunsch wrote:
> As Sergey Alyoshin wrote:
>
>> > Thus, I think the really only safe option is to compare for less than
>> > a small epsilon rather than equality.
>>
>> Maybe for clarity check against DBL_EPSILON instead of 1e-6?
>
> DBL_EPSILON didn't help …
As Sergey Alyoshin wrote:
> > Thus, I think the really only safe option is to compare for less than
> > a small epsilon rather than equality.
>
> Maybe for clarity check against DBL_EPSILON instead of 1e-6?
DBL_EPSILON didn't help … so I analyzed a bit more – and found it.
The issue is that thi
On Tue, Oct 18, 2016 at 10:17 AM, Joerg Wunsch wrote:
> As Sergey Alyoshin wrote:
>
>> > Thus, I think the really only safe option is to compare for less than
>> > a small epsilon rather than equality.
>>
>> Maybe for clarity check against DBL_EPSILON instead of 1e-6?
>
> OK, I'll give that a try.
As Joerg Wunsch wrote:
> (Layer stack script)
>
> > You can make for _each_ merged layer a project file with positioning,
> > rotation
> > and layer visibility.
>
> That doesn't help much for panelization.
OK, upon re-thinking, I guess I know what you mean.
Yes, a little more cumbersome than
As Sergey Alyoshin wrote:
> > Thus, I think the really only safe option is to compare for less than
> > a small epsilon rather than equality.
>
> Maybe for clarity check against DBL_EPSILON instead of 1e-6?
OK, I'll give that a try. I wasn't aware such constant exists.
In theory, for a true ep
On Tue, Oct 18, 2016 at 9:12 AM, Joerg Wunsch wrote:
> As Sergey Alyoshin wrote:
>
>> I can't reproduce it on 64 and 32-bit systems with file
>> example/protel-pnp/SE_SG_IF_V2.GTL
>
> It's not easy to reproduce. It happened as part of a complex panel
> (panelizing 13 sub-PCBs). When using the fi
As Sergey Alyoshin wrote:
> I can't reproduce it on 64 and 32-bit systems with file
> example/protel-pnp/SE_SG_IF_V2.GTL
It's not easy to reproduce. It happened as part of a complex panel
(panelizing 13 sub-PCBs). When using the files that caused the
problem in a single, separate project, they
On Mon, Oct 17, 2016 at 9:26 AM, Joerg Wunsch wrote:
> As Sergey Alyoshin wrote:
>
>> I have done panelization with "RS-274X Merge (Gerber)..." which use
>> merge_images().
>
> I have been using it now in order to produce a large panel.
>
> It's indeed a very nice option, thank you!
>
> I have one
As Joerg Wunsch wrote:
> + && (fabs(trans->rotation - M_PI) < 1E-6))
> + break;
> + if (fabs(trans->rotation - M_PI_2) < 1E-6
> + || fabs(trans->rotation - (M_PI+M_PI_2)) < 1E-6) {
After thinking more about
As Sergey Alyoshin wrote:
> I have done panelization with "RS-274X Merge (Gerber)..." which use
> merge_images().
I have been using it now in order to produce a large panel.
It's indeed a very nice option, thank you!
I have one suggestion: when merging the copper layers, gerbv suddenly
told me
As Sergey Alyoshin wrote:
> I have done panelization with "RS-274X Merge (Gerber)..." which use
> merge_images().
Works like a charm.
That raises the question about a new release with these fine new
features ... the previous one is now almost two years old.
--
cheers, Joerg .-.-.
As Sergey Alyoshin wrote:
> I have done panelization with "RS-274X Merge (Gerber)..." which use
> merge_images().
Cool, now I can see it under "Exports" (didn't look there before),
and I think I'm getting an idea about how to use it.
спасибо большое!
--
cheers, Joerg .-.-. --..
On Thu, Sep 22, 2016 at 3:25 PM, Joerg Wunsch wrote:
> I'm currently thinking of what would be needed to make gerbv
> a full-featured panelization tool.
>
> I think we've already got much:
>
> . a good Gerber and Excellon parser (better than many other parsers)
> . the option to translate, mirror
13 matches
Mail list logo
