• 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
Re: Beating XCode's key buffer
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Beating XCode's key buffer


  • Subject: Re: Beating XCode's key buffer
  • From: Markus Hitter <email@hidden>
  • Date: Thu, 16 Feb 2006 17:20:10 +0100


Am 16.02.2006 um 15:03 schrieb Steve Mills:

Another one that really bugs me is when I'm searching for something in a file and I quickly hit these 3 key equivs; command-e (Use Selection for Find), command-up-arrow, command-g (Find Next). The Find Next just beeps. If I give Xcode a split second to catch up with a slow, puny, inferior human, then command-g works.

My vintage PowerMac 7600 (132 MHz) is just great at detecting such race conditions and Tiger seems to have more issues in general than Jaguar here (using the same app). But who'd listen to bug reports originating from a trusty, 10 years old computer?


My other Macs are too fast to repeat the conditions reliably enough.


Markus

- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/




_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Beating XCode's key buffer
      • From: Mike Linden <email@hidden>
References: 
 >Re: Beating XCode's key buffer (From: Steve Mills <email@hidden>)

  • Prev by Date: Re: Beginner Questions (was no subject)
  • Next by Date: Xcode-way of using lipo to obtain universal binaries
  • Previous by thread: Re: Beating XCode's key buffer
  • Next by thread: Re: Beating XCode's key buffer
  • Index(es):
    • Date
    • Thread