12:21 PM, Fritz Anderson
> wrote:
>
>> On 12 Jul 2009, at 1:37 PM, Påhl Melin wrote:
>>
>> Is there a way to stop table views interpret multi-finger gestures as
>>> "single-finger" scrolling?
>>>
>>
>> I don't know for sure,
Hi,
I'm trying to implement application-wide multi-touch gestures (e.g.
two and three finger swipes in various directions) as shortcuts to
different functions in an iPhone app. When I try to recognize the
gestures in a table view I cannot get the table view to stop interpret
multi-finger gestures
Hi,
Have you noticed the new table view style used in the Spotlight search
screen in iPhone OS 3.0? The table view has rounded corners like the
grouped style but where the actual content *within* the group is
scrolled and the icons in the left column are positioned in the top
left corner while scr
2009/3/25 Benjamin Stiglitz :
>> I'm not completely satisfied using signals (especially since they are
>> not dynamically allocated and I may want to use more in the future)
>> but signals was the lowest level alternative I could think about. This
>> code will be used _very_ frequently and I want t
2009/3/25 Ken Thomases :
> Ignoring a signal doesn't prevent it from being delivered. GDB is stopping
> at the point of delivery, _before_ any decision has been made about how to
> handle the signal. The fact that the process will ignore the signal is
> something that is _about to happen_ in the
2009/3/25 Ken Thomases :
> On Mar 25, 2009, at 2:50 AM, Påhl Melin wrote:
>
>> I have a C++ singleton class where you call methods to execute
>> commands that are actually performed by a background thread. When a
>> command is "requested" it is put in a queue and
I have a C++ singleton class where you call methods to execute
commands that are actually performed by a background thread. When a
command is "requested" it is put in a queue and I use raise(SIGUSR2)
to wake-up the background thread. The reason I use signals to wake-up
the background thread is that
2008/12/5 Sherm Pendley <[EMAIL PROTECTED]>:
> On Dec 5, 2008, at 3:16 PM, Påhl Melin wrote:
>
>> 2008/12/5 Sherm Pendley <[EMAIL PROTECTED]>:
>>>
>>> You'd have far, far less trouble programming for the Mac if you'd simply
>>> learn how
2008/12/5 Sherm Pendley <[EMAIL PROTECTED]>:
> On Dec 5, 2008, at 7:52 AM, Påhl Melin wrote:
>
>> ...to have the TimerFunction() function be called twice per second
>> after 5 seconds (time in millisecond). Nothing else – you don't need
>> to idle your thread a
2008/12/5 Joseph Kelly <[EMAIL PROTECTED]>:
> From everything you've said, Påhl, you can very easily implement it using a
> combination of Cocoa and Core Foundation. I posted a response yesterday
> which you might want to look at.
Thanks Joseph. I looked at your source more closely and I think I g
2008/12/5 Jean-Daniel Dupas <[EMAIL PROTECTED]>:
>
> Le 5 déc. 08 à 16:00, Påhl Melin a écrit :
>
>> 2008/12/5 Benjamin Stiglitz <[EMAIL PROTECTED]>:
>>>>
>>>> I need to use timers in a low level library where I need to specify
>>>>
2008/12/5 Benjamin Stiglitz <[EMAIL PROTECTED]>:
>> I need to use timers in a low level library where I need to specify
>> asynchronous callbacks to a timer function. I will not have any run
>> loop so I cannot use NSTimer. Are there any low level timer API to use
>> instead? I haven't found anythi
2008/12/5 Jean-Daniel Dupas <[EMAIL PROTECTED]>:
> The dotnet timer is useless for a lots of cases for one reason: "The method
> does not execute on the thread that created the timer"
> It uses a theadpool setup by the framework in background.
In my case, I have no need at all, to run the callback
2008/12/4 Jean-Daniel Dupas <[EMAIL PROTECTED]>:
> My understanding is that ALL threads have a runloop (from the CFRunLoop
> doc):
>
> «There is exactly one run loop per thread. You neither create nor destroy a
> thread's run loop. Core Foundation automatically creates it for you as
> needed. »
>
>
2008/12/4 David Springer <[EMAIL PROTECTED]>:
> I don't mean to sound patronizing, but unless I have missed some fundamental
> premise, didn't you just re-invent DO? Maybe the right way to port this
> framework is to make your API a thin wrapper on top of Obj-C messages, and
> your set up a wrappe
2008/12/4 Julien Jalon <[EMAIL PROTECTED]>:
> The question itself does not make a lot of sense for me. A timer API is
> tightly bound to the underlying framework that is idling your thread.
> If the idling API is CFRunLoopRun(), you'd use CFTimers, if your idling API
> is select() or kevent(), you'
2008/12/4 Joseph Kelly <[EMAIL PROTECTED]>:
> I've used both the CF and NS timer apis in many different situations without
> a hitch. They're fairly reliable. Perhaps you could explain your "can't use
> a runloop" restriction -- e.g. if you are writing a daemon or a kext, this
> is not the list you
2008/12/4 Jean-Daniel Dupas <[EMAIL PROTECTED]>:
>
> Le 4 déc. 08 à 15:17, Påhl Melin a écrit :
>
>> 2008/12/4 Jean-Daniel Dupas <[EMAIL PROTECTED]>:
>>>
>>> If you want to avoid Cocoa, Cocoa-dev is probably not the best mailing
>>> list
&
2008/12/4 Jean-Daniel Dupas <[EMAIL PROTECTED]>:
> If you want to avoid Cocoa, Cocoa-dev is probably not the best mailing list
> to ask.
> You will have more chance on darwin-dev.
I don't want to avoid Cocoa, but I just haven't found any Cocoa class
that supports timers without a run loop. But may
kind of functionality yourself. You can
> then just use sleep() to make your thread wait.
>
> On 04/12/2008, at 9:32 PM, Påhl Melin wrote:
>
>> I need to use timers in a low level library where I need to specify
>> asynchronous callbacks to a timer function. I will not have
I need to use timers in a low level library where I need to specify
asynchronous callbacks to a timer function. I will not have any run
loop so I cannot use NSTimer. Are there any low level timer API to use
instead? I haven't found anything useful (yet) on google nor ADC. I
assume there must exist
Thanks, that solved the problem. I guess google is my friend...
/ Påhl
2008/11/21 Roland King <[EMAIL PROTECTED]>:
> google says this
>
> http://www.cocoabuilder.com/archive/message/xcode/2008/9/11/24570
>
> Påhl Melin wrote:
>
>> I tried to upgrade a small test p
I tried to upgrade a small test project from gcc 4.0 to gcc 4.2 by
changin the compiler version in the Project Info window but I get a
strange compiler error:
error: current namespace 'std' does not enclose strongly used
namespace '__gnu_debug_def'
... in the file which is included from . If I
c
2008/11/20 Nick Zitzmann <[EMAIL PROTECTED]>:
>
> On Nov 20, 2008, at 7:50 AM, Påhl Melin wrote:
>
>> I'm very tempted to use the new 64-bit Objective-C ABI in my next
>> project. Primarily because of the improved interoperability with C++
>> destructo
On Thu, Nov 20, 2008 at 8:55 AM, Shawn Erickson <[EMAIL PROTECTED]> wrote:
>On Thu, Nov 20, 2008 at 8:39 AM, Påhl Melin <[EMAIL PROTECTED]> wrote:
>> On Thu, Nov 20, 2008 at 7:43 AM, Shawn Erickson <[EMAIL PROTECTED]> wrote:
>>> The decision between 64b and
On Thu, Nov 20, 2008 at 7:43 AM, Shawn Erickson <[EMAIL PROTECTED]> wrote:
> The decision between 64b and 32b is made at compile time for your
> compiled code. As a result your 64b executable wont run under the 32b
> runtime not matter what you do.
>
> ...however you can of course (normally you wou
re to require the use of the 64-bit ABI in my next project,
which mac models would the application run on? And is it possible to
detect at runtime if I'm running the old 32-bit ABI or the new 64-bit
to enable a fallback on non-64-bit models?
Best Regards,
Påhl Melin
>From the "Objective
27 matches
Mail list logo
