• 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: Weird toolbar button behavior in 1.5?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Weird toolbar button behavior in 1.5?


  • Subject: Re: Weird toolbar button behavior in 1.5?
  • From: Scott Tooker <email@hidden>
  • Date: Wed, 11 Aug 2004 21:18:03 -0700

The problem with trying to have click-through some of the time is that then the user is always unsure exactly what items will activate immediately or not. There are certain things that can be done to indicate what will cause an action (like enabling/disabling widgets or mouse rollovers), but it's not foolproof.

The problem with having everything use click through is then you can accidentally cause actions that are not desired (and sometimes the visible part of the window is filled with widgets that perform actions). A simple and evil example is clickthrough into a large text view, which destroys the current cursor position and selection.

For now, we've taken the position that it's better to be consistent and not allow clickthrough in Xcode than trying to allow selective clickthrough.

Scott


On Aug 11, 2004, at 9:14 AM, Bryan Pietrzak wrote:

On Aug 10, 2004, at 2:08 PM, Ali Lalani wrote:

However, i think the behavior should be limited to:
a) Things that could cause data to be lost(i.e delete button)
b) Things that depend on a context in the window such as a selection in
a tableview(which could be hidden by other windows)

Cickthrough is generally a horrible idea, because it slows you down big time. You now have to be careful where you click on a background window, and even if you selectively enable some toolbar items in background windows, it now means I have to stop and think about those background items and whether or not they're available.


I hate it. Command-click-through? Fine. But without a modifier? Nope.

Bryan
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.


  • Follow-Ups:
    • Re: Weird toolbar button behavior in 1.5?
      • From: Bryan Pietrzak <email@hidden>
References: 
 >Re: Weird toolbar button behavior in 1.5? (From: David Dunham <email@hidden>)
 >Re: Weird toolbar button behavior in 1.5? (From: Ali Lalani <email@hidden>)
 >Re: Weird toolbar button behavior in 1.5? (From: Bryan Pietrzak <email@hidden>)

  • Prev by Date: Re: Compile
  • Next by Date: Re: Xcode 1.5 Release - Java Code Completion Issues
  • Previous by thread: Re: Weird toolbar button behavior in 1.5?
  • Next by thread: Re: Weird toolbar button behavior in 1.5?
  • Index(es):
    • Date
    • Thread