On Sat, Jan 5, 2013 at 6:59 PM, johannes hanika <[email protected]> wrote: > On Sat, Jan 5, 2013 at 4:31 AM, Jan <[email protected]> wrote: >>> >>> 2) Feature request: >>> >>> At the moment it is not possible to give absolute values for the border >>> >>> size. Is there a special reason for that, or could this possibly be >>> >>> added >>> >>> in a future version? >>> >> >>> >> absolute in centimeters? we don't do print sizes. absolute in pixels? >>> >> makes no sense to our pipeline, it processes your images at various >>> >> resolutions, and should also be copy/pastable in a meaningful way to a >>> >> downscaled version or a lower/higher megapixel camera. >>> > >>> > But remeber that actually we cannot set equal borders in all >>> > directions, as the long one is larger than the short one. Usually not >>> > a problem, for thin borders, but can be for somebody if he is trying >>> > to set a large border. So probably, we should be able to set it in >>> > pixels. If the user copy&paste it over a 200x500 image, it will get a >>> > larger border than image, but that is not a problem, IMHO. >>> >>> you'll also get a larger border when zoomed to fit than if you zoom in >>> 1:1 if you're not careful. also synchronizing with the preview >>> pipeline will be a problem. or if we decide to support large >>> resolutions for print by scaling up first and then processing. >>> >>> also i don't see how pixel sizes matter. >> >> Thanks for your comments. >> When exporting for the web, I sometimes would like to be able to specify the >> border in pixels, typically 2px to get a very thin frame that separates image >> from background. >> But I see from your comments that this seems to be a very special case. >> >> Anyways, the border should be symmetric if setting horizontal and vertical >> position to center (ie. left size = right size, top = bottom), which doesn't >> always work currently: http://www.abload.de/img/img_000199qii.jpg > > right. that sucks. it currently enforces the aspect ratio instead as > well as it can. it's rounded to integers at some point anyways, so > that's only so precise. maybe we could optimize the calculation for > equal boder sizes instead, or maybe it would need to be anti-aliased > and draw half pixel borders.
oh, thinking about it again: do you have `high quality export' enabled in your preferences? if you export a scaled-down version for the web (like 600px wide instead of 0 in the export module) that should give you exactly that: more precise borders + anti-aliased pixels. -jo ------------------------------------------------------------------------------ Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
