Le 22/11/2015 20:42, Guillermo Polito a écrit :
Out of the top of my head, doing it like that only profiles widget
creation/install if I'm not mistaken. But not render time.
Because the doit is executed inside the event processing of the morphic
render loop. But a cool ui profiling should also measure the drawOn:
methods.
I don't know if there is a tool to do that right know but it would be
possible...
Inspect the morph and do: [ self fullDrawOn: Display getCanvas ] timeProfile
If it is a FT-based morph, you may have to do a self refresh or self
changed, so that you can measure the recreation of the submorphs.
Normal GUI code has very short rendering time (a few tens of
milliseconds), except when you use large fonts and sub-pixel rendering
(LCD setting on FreeType rendering).
Thierry
Le 22 nov. 2015 20:23, "Dimitris Chloupis" <kilon.al...@gmail.com
<mailto:kilon.al...@gmail.com>> a écrit :
yeah probably , your code returns nothing too. So what we suppose to
use to profile fast code ?
On Sun, Nov 22, 2015 at 9:12 PM Nicolai Hess <nicolaih...@gmail.com
<mailto:nicolaih...@gmail.com>> wrote:
2015-11-22 20:01 GMT+01:00 Dimitris Chloupis
<kilon.al...@gmail.com <mailto:kilon.al...@gmail.com>>:
Why
[CheckboxMorph new] timeProfile
returns nothing ?
too fast?
[ 3+3 ] timeProfile
return nothing too.
try
[CheckboxMorph new openInWorld] timeProfile.
I also tried it in the profile tool without the block and
still displays nothing . Is there any special requirement
for profiling code ?
