1. profiling
- Posted by "Juergen Luethje" <j.lue at gmx.de> Feb 12, 2005
- 598 views
Hi all, the 'ex.pro' files can contain much code, that is not used by the program at all. This can considerably increase the size of the file, so that finding the lines that are actually of interest often takes rather long. I'd appreciate it very much, if 'ex.pro' files would not contain routines, that are never used by the program. Rob, what do you think? Regards, Juergen -- Have you read a good program lately?
2. Re: profiling
- Posted by Robert Craig <rds at RapidEuphoria.com> Feb 12, 2005
- 546 views
- Last edited Feb 13, 2005
Juergen Luethje wrote: > the 'ex.pro' files can contain much code, that is not used by the > program at all. This can considerably increase the size of the file, > so that finding the lines that are actually of interest often takes > rather long. > > I'd appreciate it very much, if 'ex.pro' files would not contain > routines, that are never used by the program. I know what you mean. You can manually limit the amount of profile output using: with profile without profile or with profile_time without profile_time but in many cases you'd prefer to profile everything and then have the parts that are never executed excluded automatically from the listing. You might also want the heavily executed sections to be highlighted better than they are now. I'll consider it. Probably not for 2.5 official though. Regards, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com
3. Re: profiling
- Posted by Tone Škoda <tskoda at email.si> Feb 13, 2005
- 539 views
i had just made a ".pro viewer". i'll post it soon. to me its very helpful. Juergen Luethje wrote: > > Hi all, > > the 'ex.pro' files can contain much code, that is not used by the > program at all. This can considerably increase the size of the file, > so that finding the lines that are actually of interest often takes > rather long. > > I'd appreciate it very much, if 'ex.pro' files would not contain > routines, that are never used by the program. > > Rob, what do you think? > > Regards, > Juergen > > -- > Have you read a good program lately? > >
4. Re: profiling
- Posted by Brian Broker <bkb at cnw.com> Feb 13, 2005
- 534 views
Tone Škoda wrote: > > i had just made a ".pro viewer". > i'll post it soon. > to me its very helpful. Cool! I thought about doing that once but was waiting for somebody to beat me to it. ;) -- Brian
5. Re: profiling
- Posted by Tone Škoda <tskoda at email.si> Feb 13, 2005
- 543 views
- Last edited Feb 14, 2005
I've uploaded it to my site along with some other things: http://www10.brinkster.com/tskoda/euphoria.asp Brian Broker wrote: > > Tone Škoda wrote: > > > > i had just made a ".pro viewer". > > i'll post it soon. > > to me its very helpful. > > Cool! I thought about doing that once but was waiting for somebody to beat > me to it. ;) > > -- Brian >
6. Re: profiling
- Posted by "Juergen Luethje" <j.lue at gmx.de> Feb 14, 2005
- 539 views
- Last edited Feb 15, 2005
Tone Skoda wrote: <snip> > i had just made a ".pro viewer". > i'll post it soon. > to me its very helpful. Also to me it looks very helpful, thank you! There is one little thing though. When after clicking at the [next] or [previous] button a line is highlighted that is longer than the width of the window, the text automatically scrolls to the right. Can I disable that automatic scrolling? Nevertheless I would still much appreciate to have smaller .pro files. E.g. when a program only uses one routine of an included file, the .pro file should contain only that routine, not the whole regarding file. That would make it much easier to get an *overview*. Regards, Juergen
7. Re: profiling
- Posted by Tone Škoda <tskoda at email.si> Feb 15, 2005
- 568 views
Juergen Luethje wrote: > Also to me it looks very helpful, thank you! > There is one little thing though. When after clicking at the [next] or > [previous] button a line is highlighted that is longer than the width of > the window, the text automatically scrolls to the right. Can I disable > that automatic scrolling? Just replace this new procedure with old one ("select line" part changed):
procedure jump (integer index_) integer charIndex integer line integer startIndex, endIndex CurIndex = index_ --// --// jump to line: --//=> line = Data [index_] [LINE_NUM] charIndex = sendMessage (TextEdit, EM_LINEINDEX, line - 1, 0) setFocus (TextEdit) Void = sendMessage (TextEdit,EM_SETSEL, charIndex, charIndex) --// --// select line: --//=> --// edittext_select_line (TextEdit, line) startIndex = sendMessage (TextEdit, EM_LINEINDEX, line - 1, 0) endIndex = startIndex + sendMessage (TextEdit, EM_LINELENGTH, startIndex, 0) setFocus (TextEdit) Void = sendMessage (TextEdit, EM_SETSEL, endIndex, startIndex) setFocus (TextEdit) edittext_ensure_in_center (TextEdit, line, 0) setFocus (TextEdit) statusbar_part__settext_and_resize (StatusWin, SB_CUR, sprintf ("%d/%d", {index_, length (Data)})) statusbar_part__settext_and_resize (StatusWin, SB_PERC, sprintf ("%.2f%%", {100 * Data [index_] [LINE_VAL] / Sum})) statusbar_part__settext_and_resize (StatusWin, SB_MSG, "") end procedure
8. Re: profiling
- Posted by "Juergen Luethje" <j.lue at gmx.de> Feb 16, 2005
- 547 views
Tone Skoda wrote: > Juergen Luethje wrote: > >> Also to me it looks very helpful, thank you! >> There is one little thing though. When after clicking at the [next] or >> [previous] button a line is highlighted that is longer than the width of >> the window, the text automatically scrolls to the right. Can I disable >> that automatic scrolling? > > Just replace this new procedure with old one ("select line" part changed): [code snipped] Works like a charm! Thanks, Juergen