i'm receiving memory leaks when using this code on device with
instruments. the code seems fine to me so i don't understand the
leaks. leaking objects are GSEvent and GeneralBlock-16. you can
download my small sample project i've created using the above code at
this address: http://tinyurl.com/
i'm very grateful for your help. thanks so much for posting such a
complete solution. i'm certain there will be others like myself who
will find your code extremely helpful. thanks again.
On Tue, Dec 8, 2009 at 5:24 PM, mmalc Crawford wrote:
>
> On Dec 8, 2009, at 12:33 pm, mmalc Crawford wrot
On Dec 8, 2009, at 12:33 pm, mmalc Crawford wrote:
Get the logic right...
> - (void)setUpTouchHandling {
>
>touchToLabelMapping = CFDictionaryCreateMutable (kCFAllocatorDefault, 5,
> &kCFTypeDictionaryKeyCallBacks, &kCFTypeDictionaryValueCallBacks);
>availableLabels = [[NSMutableArray a
On Dec 8, 2009, at 8:59 am, Chunk 1978 wrote:
> this is what i have so far, but i have no idea how to write the
> touchesEnded method so that the appropriate label will clear. so if 3
> fingers are touching the screen and displaying their different
> coordinates, if the 2nd finger that was press
this is what i have so far, but i have no idea how to write the
touchesEnded method so that the appropriate label will clear. so if 3
fingers are touching the screen and displaying their different
coordinates, if the 2nd finger that was pressed ends its touch, the
2nd label will clear ("Touch 2: {
On Dec 8, 2009, at 3:49 am, Chunk 1978 wrote:
> i meant that i find it complicated compared to basic single touches or
> gestures.
>
It's not clear what's complicated.
You typically want to know when touches began, moved, and ended, and there are
methods to inform you when each of these things
i meant that i find it complicated compared to basic single touches or
gestures. it's making my head swim. since it's something i would
imagine lots of developers have to deal with i'm mostly surprised that
apple hasn't made the process more convenient, but instead the docs
state that i have to u
On 08/12/2009, at 8:58 PM, Chunk 1978 wrote:
> i'm really surprised with how complicated this
> is.
Yes, because a multi-touch gesture-based events system is child's play, really.
Makes you wonder why Apple's OS is the only one to have it built in, since any
half-decent programmer could jus
thanks for the links. i'm really surprised with how complicated this
is. i'm also equally surprised that there is not a lot of small
sample code online
On Tue, Dec 8, 2009 at 3:50 AM, mmalc Crawford wrote:
>
> On Dec 8, 2009, at 12:38 am, mmalc Crawford wrote:
>
>>> is this suppose to work for
On Dec 8, 2009, at 12:38 am, mmalc Crawford wrote:
>> is this suppose to work for multiple touches where one touch is
>> already present, then another touches the screen?
>>
> Yes, it does; tested in a working application.
>
>> it's not working for me. each time i touch the screen and add an o
On Dec 7, 2009, at 7:08 pm, Chunk 1978 wrote:
> is this suppose to work for multiple touches where one touch is
> already present, then another touches the screen?
>
Yes, it does; tested in a working application.
> it's not working for me. each time i touch the screen and add an object to
>
is this suppose to work for multiple touches where one touch is
already present, then another touches the screen? it's not working
for me. each time i touch the screen and add an object to the
myTouches array the return count always returns 1, no matter how many
fingers i already have touching th
On Dec 7, 2009, at 4:12 pm, Chunk 1978 wrote:
> if ([[[event allTouches] anyObject] view] == self)
> {
> for (UITouch *touch in touches)
> {
> CGPoint touchPoint = [[touches anyObject]
> locationInView:self];
>
13 matches
Mail list logo
