• 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: Two ways to get this NSTableView behaviour but I do not know how to implement either
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Two ways to get this NSTableView behaviour but I do not know how to implement either


  • Subject: Re: Two ways to get this NSTableView behaviour but I do not know how to implement either
  • From: Gerben Wierda <email@hidden>
  • Date: Sat, 12 Oct 2002 22:23:00 +0200

On Saturday, Oct 12, 2002, at 21:03 Europe/Amsterdam, Andreas Mayer wrote:

But maybe I don't understand what you are trying to do at all. So what are you going to put inside that table view and what is the user supposed to be able to do with it?

So what are you going to put inside that table view and what is the user supposed to be able to do with it?

I would like to present a user with a set of items which is variable in length (and can be pretty large, as in 20-30) to be selected or deselected. The set starts out in a state where certain items are already selected (the current set) and can be changed by the user. The fact that the table view currently starts out with, say, items 1-4,8,26 selected.

This would be best presented as a 'variable list of checkboxes'. You start out with a set of choices, and you modify that. In other words, you are presented with a set of options, either turned off or on and it starts out with the currently active options as selected. So, what happens then is that a user selects an extra option or deselects an active option, and currently - due to default NSTableView behaviour - as a side effect, all other already selected options at the start of the table view are deselected. This is confusing, because most of those options were never seen by the user (outside the scroll area). So, the user selects a new item and does not notice that all others that are already selected at the start are deselected.

Maybe I should add: this is presented to *very* non-technical users and I must assume *very* little computer literacy. In fact, I did present a beta group with the standard table view solutions and it turned out it was confusing.

Were it a fixed set op options, it would be implemented with checkboxes. But the set has a variable length, so I need a table view solution that behaves like checkboxes (single itemn select and deselect), or in other words, the way a table view would behave when every event was a Cmd-click.

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

  • Follow-Ups:
    • Re: Two ways to get this NSTableView behaviour but I do not know how to implement either
      • From: Scott Anguish <email@hidden>
    • Re: Two ways to get this NSTableView behaviour but I do not know how to implement either
      • From: Andreas Mayer <email@hidden>
    • Re: Two ways to get this NSTableView behaviour but I do not know how to implement either
      • From: Cameron Hayne <email@hidden>
References: 
 >Re: Two ways to get this NSTableView behaviour but I do not know how to implement either (From: Andreas Mayer <email@hidden>)

  • Prev by Date: DB Front-end design in Cocoa
  • Next by Date: Re: App crashes on thread exit
  • Previous by thread: Re: Two ways to get this NSTableView behaviour but I do not know how to implement either
  • Next by thread: Re: Two ways to get this NSTableView behaviour but I do not know how to implement either
  • Index(es):
    • Date
    • Thread