• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Handling User Generated Tablet Events
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Handling User Generated Tablet Events


  • Subject: Handling User Generated Tablet Events
  • From: "Carmen C. Cerino Jr." <email@hidden>
  • Date: Sun, 27 Jan 2008 13:40:17 -0500

Howdy,

I am working on a project that involves utilizing tablet events. I wrote a project that generates tablet events using the Quartz Event Services API. Currently I believe that part of my project is fine. After writing that portion of the project I decided to create some demo apps that utilize tablet events in order to test my event producing app. I have three different types of demo applications: Carbon, Cocoa, Quartz Composer. My Carbon app works just fine. I installed 2 event handlers for the two different types of tablet events. My handler functions are very basic. All they do is print out the deviceID field associated with that tablet event. The QC application is a particle system with a tablet controller attached by the x and y values. Unfortunately this app does not work. I have no knowledge about QC. The QC app was a suggestion by a colleague for a demo app.

The Cocoa app is a little more of a step up. I took the CIMicropaint demo app found in the Quartz Example folder and attempted to swap out the mouse down and mouse dragged events for the tablet proximity and tablet point events respectively. If I am reading the Cocoa event handler guide right, event handlers in Cocoa do not have to be registered like they do in Carbon. In order to supply event handlers, one would just needs to override the proper message(function). With this assumption in mind, I renamed the moseDown message to tabletProximity and the mouseDragged message to tabletPoint. Unfortunately this is not working for me. According to Instrument's Cocoa Event Monitoring tool, the tablet events are arriving to the app, but it seems like the app is not passing them out to the handlers. I am new to Apple development, and all of the dev I have done up until this point has been with Carbon. I am doing my best to track down the issue, but my limited knowledge of Obj-C and the Cocoa framework has gotten me stuck in a rut.

I would appreciate any suggestions that anyone may have to help me track down a solution to this issue. Thoughts on who else I could talk to about this issue would also be greatly appreciated. I have heard mention about positing issues that no one in the list has answers to as bugs in the bug reporting system. How well does this work? I will glad to share my any of code in order to help facilitate a solution. Please let me know what you would like to see, and i would be glad to send it.

Cheers,
Carmen
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Handling User Generated Tablet Events
      • From: Bill Cheeseman <email@hidden>
  • Prev by Date: designing beyond MV and (one) C
  • Next by Date: Re: designing beyond MV and (one) C
  • Previous by thread: Re: stringByReplacingOccurrencesOfString in Tiger
  • Next by thread: Re: Handling User Generated Tablet Events
  • Index(es):
    • Date
    • Thread