[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: AW: koffice/kspread
From:       David Faure <dfaure () klaralvdalens-datakonsult ! se>
Date:       2004-01-06 11:50:55
Message-ID: 200401061250.55560.dfaure () klaralvdalens-datakonsult ! se
[Download RAW message or body]

On Tuesday 06 January 2004 10:14, Philipp Müller wrote:
> Hello David,
> 
> please revert as it does make sense in the second view.
Please consider the arguments below first :)

> Reasons:
> 1. How it behaves now:
> It stops now somewhere in the middle of the sheet. Where should it stop? In the \
> last filled row? In the last filled cell in your column?  What if I'm already below \
> the last filled row/cell? 

Ctrl+Down stops at the last cell that is like the current one (empty, or non-empty).
If you are in filled cells in a column, it stops at the last consecutively-filled \
cell (i.e. right before the first empty cell it finds). If you are already below the \
last filled cell, then why on earth should it go to row 32767? There's nothing under \
the current cell that can be of any interest (as far as Ctrl+Down is concerned).

> What if this cell is not filled but has a lot of cells filled left and right of it? \
> 
Why should this have any relation? I'm going down in one column, other columns don't \
matter. If one wants to keep going down because other rows have stuff, then this \
isn't the right keypress, and one should use Down or PgDown - or move to the column \
with more stuff and Ctrl+Down.

> Or should it stop at the end of the screen?

Now that's a good idea, I'd love that. It's a little bit more difficult to code \
though.

> For me the new behaviour and any other similar behaviour is not really predictable \
> and rather confusing.

I don't understand what's not predictable about it. It's very predictable, as shown \
above. If you're on an empty cell, it's supposed to look for a non-empty cell and \
stop right before it. Why should row 32768 (which doesn't exist) be treated like a \
row with non-empty cells? If Ctrl+Down can't find a non-empty cell, then it shouldn't \
go down.

> 2. If it stops at the sheet ends, then it gives you at least the information: This \
> is the end, there are no filled cells left.  This information is not available in \
> the new way. 
If Ctrl+Down doesn't move the active cell, then you have the same information: no \
more filled cells under there. 

> And you can always easily jump back with 1 single ctrl-up/left. 
And you can easily start typing text by mistake at row 32767, if you were doing
a repetitive operation like Down / Ctrl+V / Down / Ctrl+V.
By mistake one ends up pressing Ctrl while pressing Down, and ends up
pasting stuff at row 32767.  This is what got me into fixing this broken behavior.

> Trust me, I'm using ctrl-down/right regularly in my daily work 
I'm using it regularly too, and it ALWAYS annoys me when it goes to row 32767. Why on \
earth would I want to be there? If you want visual indication that Ctrl+Down was \
pressed but that it has nowhere to go to, then make the active-cell indicator blink \
red, or something like that :)

> And yes, all other 3 spread sheet apps I tested behave this way as well.
This is usually an argument that works - when the behavior isn't braindead :)

> And finally, we have discussed this long ago. See \
> http://lists.kde.org/?l=koffice-devel&m=101696042024044&w=2
Yes, and I didn't jump in at the time since I had no opinion back then :)

-- 
David Faure -- faure@kde.org, dfaure@klaralvdalens-datakonsult.se
Qt/KDE/KOffice developer
Klarälvdalens Datakonsult AB, Platform-independent software solutions
_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


[prev in list] [next in list] [prev in thread] [next in thread]