Subject | Re: spreadsheet ergonomics |
From | Snit |
Date | 04/04/2017 23:20 (04/04/2017 14:20) |
Message-ID | <D5095C2F.9CC35%usenet@gallopinginsanity.com> |
Client | |
Newsgroups | comp.os.linux.advocacy |
Follows | owl |
Followups | owl (1h & 18m) > Snit |
owlBut you will not show the type work we have been doing with multiple tables all showing and being interrelated and updating automatically?
Snit <usenet@gallopinginsanity.com>wrote:Snitowl
On 4/3/17, 9:45 PM, in article zb3ugoa00.aulu@rooftop.invalid, "owl" <owl@rooftop.invalid>wrote:
...SnitowlowlSnit
You haven't shown any benefit to that.
Sure I have... it allows you to group logically separate concepts into separate tables on the same sheet, it allows you to have data where columns do not line up, etc. I focused on this in the video on the magic spell calculation.
And I do all of that using separate windows, possibly embedded into a single window.
So show it... including the creation process. THAT will show the benefits you are missing... the ease of use.
Here's a creation process for you:
https://vid.me/pG0C
zero to 52000 tables in 2.57 seconds. Each with locked labels and formulas. Instantaneous jump to any table.
Very, very poorly, sure (as shown by the context I have returned... which you snipped). Really, you offered no REASONABLE solution.owlSnitSnitowl
With YOUR suggestion, with an open source tool, we saw the hazard: an unknowing person could have lost data. Twice.
We saw you move the goalposts beyond the specifications.
Yeah, I merely noted I wanted an open file to be renamed
And that specification was met.
-- Personal attacks from those who troll show their own insecurity. They cannot use reason to show the message to be wrong so they try to feel somehow superior by attacking the messenger.Snit
, I did not note I wanted this done in a way that would not lose data in that file and others. This, of course, would be simply assumed by any reasonable person... but you did not. It is quite telling as to how you see technology... almost as if you want to think like a computer and not assume basic knowledge and only go with what the "programmer" tells you. I mean, really, the concept that the task should NOT lead to repeated data loss in multiple files is NOT a specification that should have to be stated. It would be insane to try to list EVERY single simple assumption like that.