At 11:48 PM -0500 3/3/04, LionScribe wrote:
With MemHandleLock, once it's locked, if you lock it again it doesn't take
too much time, it basically just increments the lock count. Therefore, you
do not have to make dramatic change to your code, just lock it once before
you call a stack of functions,
With MemHandleLock, once it's locked, if you lock it again it doesn't take
too much time, it basically just increments the lock count. Therefore, you
do not have to make dramatic change to your code, just lock it once before
you call a stack of functions, and unlock it when it's done.
LionScribe
"
Thanks for all your help, both answers were very helpful, exactly what I was
looking for.
Kevin
"Flex" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
> Concentrate your efforts on MemHandleLock - it's hell slow operation. If
> you can avoid some of the locks (by pre-locking for examp
Concentrate your efforts on MemHandleLock - it's hell slow operation. If
you can avoid some of the locks (by pre-locking for example) you'll be
happy.
Also if you can share one single buffer for all your... hm... records? I
mean allocate the maximum length and save a couple of new/lock/unlock/fr
At 07:07 PM 3/1/2004, you wrote:
> -- Ben Combee, senior DTS engineer, PalmSource, Inc.
Hey Ben, do you have a new job?! Congratulations :)
I can guess what this means for the future of Codewarrior for Palm OS since
you were pretty much the whole team working on the Palm part... ( But you
probabl
> -- Ben Combee, senior DTS engineer, PalmSource, Inc.
Hey Ben, do you have a new job?! Congratulations :)
I can guess what this means for the future of Codewarrior for Palm OS since
you were pretty much the whole team working on the Palm part... ( But you
probably wont be able to dicuss that any
At 06:00 PM 3/1/2004, you wrote:
Also, is the function "TimGetTicks()" an effective way to measure
performance of a single or small number of operations, or is this an
imprecise measurement?
TimGetTicks is really only appropriate for operations that take several
seconds or more to run. Since it
My app is a little slower than I want it to be. There are some things that I
think I can do a little better to speed it up. I was wondering what common
operations on the palm take the most amount of time. These are some of the
operations that I am using in my function, but feel free to mention ot
