[visionegg] Re: hundrets of ms lost time
- From: Christoph Lehmann <lehmann@xxxxxxxxxxxx>
- To: visionegg@xxxxxxxxxxxxx
- Date: Thu, 08 May 2003 20:56:25 +0200
finally I got the problem: it is the viewport.draw() routine.
No idea what goes wrong there, in the sense, that this routine sometimes
takes more than 800ms... I will see at the code now, but if you,
Andrew, or anybody else, knowing the code well, can help me...thanks a
lot
cheers
christoph
On Thu, 2003-05-08 at 18:50, Christoph Lehmann wrote:
> Dear Andrew
> o.k. I continued to find, where my code looses time. Sadly I found, that
> it is in these commands:
>
> stimulus.parameters.texture = preloaded_texture_list[stim_index]
> screen.clear()
> viewport.draw()
> swap_buffers()
>
> if I log the time before and after this commands, I get the lost time:
> sometimes even several 100ms, usually between 16 and roughly ms (even
> thoug no sync buffer swaps is choosen...)
>
> please let me know, why these subroutines take so much time. I iwll now
> go further to see, which command exactly has the problem (maybe the
> stimulus.parametes.texture)
>
> Thanks
>
> p.s. I sent a mail to the SDL list considering getting the mouse-events
> while in max_priority mode
>
> Cheers
>
> Christoph
--
Christoph Lehmann <lehmann@xxxxxxxxxxxx>
University Hospital of Clinical Psychiatry
======================================
The Vision Egg mailing list
Archives: //www.freelists.org/archives/visionegg
Website: http://www.visionegg.org/mailinglist.html
Other related posts:
