On Tue, Oct 18, 2016 at 10:17 AM, Joerg Wunsch <j...@uriah.heep.sax.de> 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.  I wasn't aware such constant exists.
> In theory, for a true epsilon, the difference would need to be divided
> by the base value, but since all relevant base values (π/2, π·3/2) are
> close enough to 1, I think this step can be skipped.
> (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.  There's two kind of layer
> groups: one group forming each sub-board, each using the same
> translation / rotation values (to be defined / refined while
> panelizing), and one group forming each output layer.  In order to be
> useful, all the input layers need to be present in a single project.
> Thanks for your response anyway, so at least, I know there's no easy
> and obvious option I've been missing.  The merge feature itself is
> already useful enough as it is now, so a „болшое спасибо“ to you for
> implementing it.

I am not the original author, just fixing some bugs.

> Maybe I should ask again for release plans, so this nice feature could
> be more publically announced. ;-)

Export with merge was added in 2011 (and not by me).
I don't have release plans, but gerbv should be checked and released.

Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Gerbv-devel mailing list

Reply via email to