Re: [Libosmscout-development] GDI drawing Performance Under Windows

[David H. R. <dav...@gm...>]

Hi,

Well I was talking about the generic MapPaint library.

Every DrawArea/DrawWay loops for all areas/ways available. I think they
don't have any relationship between them so the loop can me split in the
computer processors to speed things up. Also GDI itself could be speed up
as Tim says.

Regards.

On Thu, 30 Dec 2021 at 13:19, Lukáš Karas <luk...@ce...> wrote:

> Hi David.
>
> Dne čtvrtek 30. prosince 2021 13:02:03 CET David Huelves Ramos napsal(a):
> > Getting the information.:
> >
> > [image: image.png]
> >
> > The bottleneck is drawing areas + drawing ways.
> >
> > Zoom in -> increments drawingways calculation time
> > Zoom out -> increments DrawingAreas calculation time.
> >
> > Both functions are a loop that is using just 1 thread from 1 processor.
> It
> > can be as all the loops implemented using Parallelism...
>
> It depends if GDI drawing methods allows parallel access. It is not
> supported
> in drawing libraries usually... Did you try to run profiler to see where
> the
> time is spend? If it is in GDI or osmscout...
>
> Lukas
>
> > On Thu, 30 Dec 2021 at 12:25, David Huelves Ramos <
> dav...@gm...>
> >
> > wrote:
> > > Hello,
> > >
> > > After googling a little this does the trick:
> > >
> > > [image: image.png]
> > >
> > > Now I get a console opened with cout/cerr redirected to it.
> > >
> > > On Thu, 30 Dec 2021 at 11:12, Tim Teulings <ti...@fr...> wrote:
> > >> Hi David,
> > >>
> > >> > Any Ideas?
> > >>
> > >> That should work. Is this possibly a Windows specifica? Is your
> > >> application linked as desktop or console application (WinMain vs.
> Main)?
> > >>
> > >> Do you see logs from the demo appliacations?
> > >>
> > >> --
> > >> Gruß...
> > >>
> > >>     Tim
> > >>
> > >> _______________________________________________
> > >> Libosmscout-development mailing list
> > >> Lib...@li...
> > >> https://lists.sourceforge.net/lists/listinfo/libosmscout-development