Benoit Gr�goire <[EMAIL PROTECTED]> writes: > On February 3, 2003 04:09 pm, Chris Morgan wrote: > > There is no need to handle select and unselect signals as the actual > > selection of rows is performed internally to the clist, the signals are > > only if you want to take action upon selection/unselection. Basically the > > user would select multiple rows either using the manual text search and > > highlight box, or by holding the space bar and highlighting rows, then they > > double click to sort the selected rows into an account. > > That IS my point. Currently, we take actions when a row is selected, actually > three different actions, depending in which row the user clicked. It's > implemented using the select signals. What do you plan to replace this with? > There is no "clicked" or "double-clicked" signal for a row anywhere in the > GTK docs. Anyhow, I presume you'd somehow replace the actions currently > taken by a simple click by double clicking in the same column. I see two > issues with this.
Can I comment as a user that I found it initially extremely confusing and later just frustrating and askward that so many actions occured on a single click. Traditionally single clicks on items only selected items to operate on. As it is in Gnucash when I accidentally click on a transaction I'm now kind of stuck editing that transaction and Gnucash won't let me finish unless I meet certain criteria. And it doesn't seem to have a concept of not having any transactions selected. I'm talking primarily about the matcher window but to a certain degree also the register and probably other windows as well. There's an awful lot of aggresively modal UIs in Gnucash that I find disconcerting and awkward when I'm not doing precisely what the programmers expected me to do. -- greg _______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
