On 20 August 2013 15:27, johannes hanika <[email protected]> wrote: > On Tue, Aug 20, 2013 at 5:25 AM, Daniel J Blueman <[email protected]> wrote: >> On 20 August 2013 01:46, Tobias Ellinghaus <[email protected]> wrote: >> > Am Sonntag, 18. August 2013, 23:32:18 schrieb Daniel J Blueman: >> >> On high-res displays, we need to increase the default "maximum width >> >> of image drawing area" and for height also. >> >> >> >> Since most users probably have more powerful processors with larger >> >> displays, I see there is good rationale to default this to unset, ie >> >> unlimited, rather than the current default, no? >> > >> > There is no such thing as unlimited. >> >> What I mean by 'unlimited' is that we don't specify a value (or we >> state 0 means unlimited) and the drawing area width is whatever size >> the interior of the window is. >> >> Does this make sense? > > the problem is that you can't change that value without quite some overhead > (you'll invalidate all cached mipmaps). more precise auto detection on first > startup might make sense (depending on screen size and cpu/gpu power).
I see. So, I set it to 4096x4096, arbitrarily larger then the resolution of my retina screen, as it's unclear how to determine actual window interior size. Thus is it generating mipmaps of this size and down, regardless of the maximised window size? -- Daniel J Blueman ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
