On Sun, 5 Feb 2023 21:04:25 +0100, "Carlos E.R."
<robin_listas@es.invalid> wrote:

>On 2023-02-05 20:26, Ken Blake wrote:
>> On Sat, 4 Feb 2023 19:57:16 +0100, "Carlos E.R."
>> <robin_listas@es.invalid> wrote:
>>
>>> On 2023-02-04 18:59, The Real Bev wrote:
>>>> On 2/3/23 9:41 PM, Thomas wrote:
>>>>> On Saturday, February 4, 2023 at 3:03:01 AM, The Real Bev wrote:
>>>>>
>>>>>>  I see no need for a snotty response to a non-snotty message.
>>>>>
>>>>> Have you never seen what Ken Blake often posts or are you basing your
>>>>> assessment of his MENSA like genius on this one thread where he showed
>>>>> true
>>>>> talent for misunderstanding how to move icons on his phone's home screen.
>>>>
>>>> I don't read everything.  Ken Blake has been here for a long time and
>>>> has offered useful information.  Using software devised by others
>>>> frequently provides annoying surprises because we do not all think the
>>>> same way.  We have blind spots, which is why it's good to have
>>>> proofreading done by someone who didn't write the material.
>>>>
>>>> There ARE dumb questions, but there are more dumb answers.
>>>
>>> I have been using computers since maybe 1980, if one can consider a
>>> programmable calculator a computer (a TI 57 or 58). I did programming
>>> for a living for some time. Yet, when I bought my first Android smart
>>> phone, a Samsung Mini 2 (plus?), and got my first call, I was unable to
>>> answer it. Nothing worked.
>>
>> I've been using computers for 60 years--since 1962. I started working
>> as a programmer then and was a computer professional with various jobs
>> until I retired in 1993. These days, I know Windows well, and also
>> several programs (Microsoft and third-party) that run under it, but
>> what I still know the least about is how to use my Android smart
>> phone.
>>
>>
>>> I think I phoned back and asked my friend how the heck was I supposed to
>>> answer a call, if pressing the button doesn't work. "You have to slide
>>> it to the side". One side (red) to cancel, another (green) to accept.
>>>
>>> Argh.
>>
>> On my Android phone (Pixel 4a) I have to slide it up. To me, that's
>> very counterintuituve. I couldn't figure out how to do it until
>> someone here (Vanguard, I think) told me how.
>
>Thinking later, I see that it is better, can't happen by accident, as
>can happen to a push button.
>
>
>>
>>
>>> It is obvious once you know it. Different user paradigm than a computer.
>>
>>
>> It *is* a computer, as far as I'm concerned, just a very small one.
>> But yes, it's a very different user paradigm from a Windows computer,
>> and that's a good part of the reason I know relatively little about
>> it.
>
>I meant a "normal" computer :-D

OK.

On Sun, 5 Feb 2023 13:04:34 -0700, AJL <noemail@none.com> wrote:

>On 2/5/2023 12:26 PM, Ken Blake wrote:
>> On Sat, 4 Feb 2023 19:57:16 +0100, "Carlos E.R."
>
>>> I think I phoned back and asked my friend how the heck was I
>>> supposed to answer a call, if pressing the button doesn't work.
>>> "You have to slide it to the side". One side (red) to cancel,
>>> another (green) to accept.
>
>>> Argh.
>
>> On my Android phone (Pixel 4a) I have to slide it up. To me, that's
>> very counterintuituve. I couldn't figure out how to do it until
>> someone here (Vanguard, I think) told me how.
>
>On my phone (Galaxy S10+) there's a setting that when set allows me to
>answer the phone by simply pushing the up button on the case. I don't
>have to look at or touch the screen at all. Check yours, maybe you have
>such a setting. It's very handy, especially on the freeway... 8-O

Getting my phone out of my pocket while I'm driving would be a giant
problem for me. But my phone connects to my car via bluetooth, and
it's very quick and easy to answer it on the dashboard.

On 2/5/23 11:26 AM, Ken Blake wrote:
> On Sat, 4 Feb 2023 19:57:16 +0100, "Carlos E.R."
> <robin_listas@es.invalid> wrote:
>>On 2023-02-04 18:59, The Real Bev wrote:
>>> On 2/3/23 9:41 PM, Thomas wrote:
>>>> On Saturday, February 4, 2023 at 3:03:01 AM, The Real Bev wrote:
>>>>
>>>>>  I see no need for a snotty response to a non-snotty message.
>>>>
>>>> Have you never seen what Ken Blake often posts or are you basing your
>>>> assessment of his MENSA like genius on this one thread where he showed
>>>> true
>>>> talent for misunderstanding how to move icons on his phone's home screen.
>>>
>>> I don't read everything.  Ken Blake has been here for a long time and
>>> has offered useful information.  Using software devised by others
>>> frequently provides annoying surprises because we do not all think the
>>> same way.  We have blind spots, which is why it's good to have
>>> proofreading done by someone who didn't write the material.
>>>
>>> There ARE dumb questions, but there are more dumb answers.
>>
>>I have been using computers since maybe 1980, if one can consider a
>>programmable calculator a computer (a TI 57 or 58). I did programming
>>for a living for some time. Yet, when I bought my first Android smart
>>phone, a Samsung Mini 2 (plus?), and got my first call, I was unable to
>>answer it. Nothing worked.

We got our first one in 1977. Hubby wrote assemblers and
cross-assemblers for sale until the chip manufacturers figured they'd
been missing out on a nice revenue source and wrote their own. I put
dBaseII on it to do a project. Later on I took a FORTRAN course. I
hate programming. REALLY hate it. I just don't think with the required
granularity.

I eventually because what was known as a "power user". Not much money
in that :-(

> I've been using computers for 60 years--since 1962. I started working
> as a programmer then and was a computer professional with various jobs
> until I retired in 1993. These days, I know Windows well, and also
> several programs (Microsoft and third-party) that run under it, but
> what I still know the least about is how to use my Android smart
> phone.
>
>>I think I phoned back and asked my friend how the heck was I supposed to
>>answer a call, if pressing the button doesn't work. "You have to slide
>>it to the side". One side (red) to cancel, another (green) to accept.

That sounds very familiar :-( I can't remember how I learned about
sliding, but I know I had to return the first half-dozen or so calls I
received.

>>Argh.
>
> On my Android phone (Pixel 4a) I have to slide it up. To me, that's
> very counterintuituve. I couldn't figure out how to do it until
> someone here (Vanguard, I think) told me how.
>
>>It is obvious once you know it. Different user paradigm than a computer.
>
> It *is* a computer, as far as I'm concerned, just a very small one.
> But yes, it's a very different user paradigm from a Windows computer,
> and that's a good part of the reason I know relatively little about
> it.

Mine is mostly a camera. A lot of the other quasi-useful functions just
don't work as well as they should or throw up ads that make the app
itself useless.

--
Cheers, Bev
"I don't think they could put him in a mental hospital.
On the other hand, if he were already in, I don't think
they'd let him out." -- Greek Geek

On 2/5/23 12:04 PM, Carlos E.R. wrote:
> On 2023-02-05 20:26, Ken Blake wrote:

>> On my Android phone (Pixel 4a) I have to slide it up. To me, that's
>> very counterintuituve. I couldn't figure out how to do it until
>> someone here (Vanguard, I think) told me how.
>
> Thinking later, I see that it is better, can't happen by accident, as
> can happen to a push button.

Indeed. I somehow accidentally paused my Ski Tracks app for 4 or 5 runs
the other day, probably missing the ACTUAL top speed I hit -- I hope. I
always blank the screen before putting it back in my pocket, so I don't
see how I could have accidentally hit the pause icon, but it happened.

>>> It is obvious once you know it. Different user paradigm than a computer.

Android apps are on the whole pretty intuitive -- a good thing, because
nobody can write instruction manuals any more. If the authors would
just stop lying it would be a big step forward.

>> It *is* a computer, as far as I'm concerned, just a very small one.
>> But yes, it's a very different user paradigm from a Windows computer,
>> and that's a good part of the reason I know relatively little about
>> it.

Last time I used windows regularly was win95. It was OK. Then I
switched to slackware (always use the system your live-in help does).

> I meant a "normal" computer :-D

Linux, obviously.

--
Cheers, Bev
"I don't think they could put him in a mental hospital.
On the other hand, if he were already in, I don't think
they'd let him out." -- Greek Geek

On 2/5/2023 1:04 PM, Carlos E.R. wrote:
> On 2023-02-05 20:26, Ken Blake wrote:

>> On my Android phone (Pixel 4a) I have to slide it up. To me,
>> that's very counterintuituve. I couldn't figure out how to do it
>> until someone here (Vanguard, I think) told me how.

> Thinking later, I see that it is better, can't happen by accident,
> as can happen to a push button.

As indicated by my other post I do use a push button (up button) to
answer my phone. Never had a problem. My phone audibly tells me who is
calling during the ring so if I don't want to answer I push the on/sleep
button and it stops the ring but not the call. The call then goes to
voicemail for perusal and a possible return later.

I've never had a problem accidentally pushing the on/sleep button
either, have you...

On 2/5/2023 1:36 PM, Ken Blake wrote:
> On Sun, 5 Feb 2023 13:04:34 -0700, AJL <noemail@none.com> wrote:
>> On 2/5/2023 12:26 PM, Ken Blake wrote:
>>> On Sat, 4 Feb 2023 19:57:16 +0100, "Carlos E.R."

>>>> I think I phoned back and asked my friend how the heck was I
>>>> supposed to answer a call, if pressing the button doesn't work.
>>>> "You have to slide it to the side". One side (red) to cancel,
>>>> another (green) to accept.

>>>> Argh.

>>> On my Android phone (Pixel 4a) I have to slide it up. To me,
>>> that's very counterintuituve. I couldn't figure out how to do it
>>> until someone here (Vanguard, I think) told me how.

>> On my phone (Galaxy S10+) there's a setting that when set allows
>> me to answer the phone by simply pushing the up button on the case.
>> I don't have to look at or touch the screen at all. Check yours,
>> maybe you have such a setting. It's very handy, especially on the
>> freeway... 8-O

> Getting my phone out of my pocket while I'm driving would be a giant
> problem for me.

Time for a belt case. My phone pops out easily no matter where I am. But
the freeway thing was supposed to be a joke...note the emoticon...

> But my phone connects to my car via bluetooth, and it's very quick
> and easy to answer it on the dashboard.

Does your Bluetooth work in the grocery store? But never mind.

Carlos was the one who wanted a button (above) so maybe his phone'll
have the magic setting...

On 2023-02-05 22:24, The Real Bev wrote:
> On 2/5/23 12:04 PM, Carlos E.R. wrote:
>> On 2023-02-05 20:26, Ken Blake wrote:
>
>>> On my Android phone (Pixel 4a) I have to slide it up. To me, that's
>>> very counterintuituve. I couldn't figure out how to do it until
>>> someone here (Vanguard, I think) told me how.
>>
>> Thinking later, I see that it is better, can't happen by accident, as
>> can happen to a push button.
>
> Indeed.  I somehow accidentally paused my Ski Tracks app for 4 or 5 runs
> the other day, probably missing the ACTUAL top speed I hit -- I hope.  I
> always blank the screen before putting it back in my pocket, so I don't
> see how I could have accidentally hit the pause icon, but it happened.
>
>>>> It is obvious once you know it. Different user paradigm than a
>>>> computer.
>
> Android apps are on the whole pretty intuitive -- a good thing, because
> nobody can write instruction manuals any more.  If the authors would
> just stop lying it would be a big step forward.

They are intuitive, after the initial shock. Then yes, everything is
intuitive.

I know people that can't handle it, so for them it is not intuitive at
all, and ask me how do I install Whatsapp, then how I open whatsapp. If
the icon doesn't fit in the first "worskpace" and is in the second, they
don't find it. Need to be told how to slide to the second space.

>
>>> It *is* a computer, as far as I'm concerned, just a very small one.
>>> But yes, it's a very different user paradigm from a Windows computer,
>>> and that's a good part of the reason I know relatively little about
>>> it.
>
> Last time I used windows regularly was win95.  It was OK.  Then I
> switched to slackware (always use the system your live-in help does).
>
>> I meant a "normal" computer :-D
>
> Linux, obviously.

For me, yes, although I sometimes have to use Windows. Both are similar
in the user interface: double click icons, mouse, etc. A "normal
computer" in this context is a desktop computer, a laptop, running whatever.

--
Cheers, Carlos.

On 2023-02-05 22:26, AJL wrote:
> On 2/5/2023 1:36 PM, Ken Blake wrote:
>> On Sun, 5 Feb 2023 13:04:34 -0700, AJL <noemail@none.com> wrote:
>>> On 2/5/2023 12:26 PM, Ken Blake wrote:
>>>> On Sat, 4 Feb 2023 19:57:16 +0100, "Carlos E.R."
>
>>>>> I think I phoned back and asked my friend how the heck was I
>>>>> supposed to answer a call, if pressing the button doesn't work.
>>>>> "You have to slide it to the side". One side (red) to cancel,
>>>>> another (green) to accept.
>
>>>>> Argh.
>
>>>> On my Android phone (Pixel 4a) I have to slide it up. To me,
>>>> that's very counterintuituve. I couldn't figure out how to do it
>>>> until someone here (Vanguard, I think) told me how.
>
>>> On my phone (Galaxy S10+) there's a setting that when set allows
>>> me to answer the phone by simply pushing the up button on the case.
>>> I don't have to look at or touch the screen at all. Check yours,
>>> maybe you have such a setting. It's very handy, especially on the
>>> freeway...  8-O
>
>> Getting my phone out of my pocket while I'm driving would be a giant
>>  problem for me.
>
> Time for a belt case. My phone pops out easily no matter where I am. But
> the freeway thing was supposed to be a joke...note the emoticon...
>
>> But my phone connects to my car via bluetooth, and it's very quick
>> and easy to answer it on the dashboard.
>
> Does your Bluetooth work in the grocery store? But never mind.
>
> Carlos was the one who wanted a button (above) so maybe his phone'll
> have the magic setting...

No, I don't want a button. What I say is that the first time I got a
call I could not answer it because the button did not respond to
pressing it. Once I knew I had to slide it, sliding became intuitive,
and I miss it when I have to press instead.

--
Cheers, Carlos.

On 2/5/23 1:41 PM, Carlos E.R. wrote:
> On 2023-02-05 22:24, The Real Bev wrote:

>> Last time I used windows regularly was win95.  It was OK.  Then I
>> switched to slackware (always use the system your live-in help does).
>>
>>> I meant a "normal" computer :-D
>>
>> Linux, obviously.
>
> For me, yes, although I sometimes have to use Windows. Both are similar
> in the user interface: double click icons, mouse, etc. A "normal
> computer" in this context is a desktop computer, a laptop, running whatever.

Something with a real keyboard -- one we can use with our eyes closed
most of he time; I never did learn to touch-type numbers and symbols.

--
Cheers, Bev
Guns kill people like spoons make Rosie O'Donnell fat.

On 2023-02-05 23:14, The Real Bev wrote:
> On 2/5/23 1:41 PM, Carlos E.R. wrote:
>> On 2023-02-05 22:24, The Real Bev wrote:
>
>>> Last time I used windows regularly was win95.  It was OK.  Then I
>>> switched to slackware (always use the system your live-in help does).
>>>
>>>> I meant a "normal" computer :-D
>>>
>>> Linux, obviously.
>>
>> For me, yes, although I sometimes have to use Windows. Both are similar
>> in the user interface: double click icons, mouse, etc. A "normal
>> computer" in this context is a desktop computer, a laptop, running
>> whatever.
>
> Something with a real keyboard -- one we can use with our eyes closed
> most of he time;  I never did learn to touch-type numbers and symbols.

Yes, a real keyboard, that's key. Heh, pun intended :-)

Numbers I can almost touch-type. Symbols, no.

--
Cheers, Carlos.

On Sun, 5 Feb 2023 13:24:29 -0800, The Real Bev <bashley101@gmail.com>
wrote:

>On 2/5/23 12:04 PM, Carlos E.R. wrote:
>> On 2023-02-05 20:26, Ken Blake wrote:
>
>>> On my Android phone (Pixel 4a) I have to slide it up. To me, that's
>>> very counterintuituve. I couldn't figure out how to do it until
>>> someone here (Vanguard, I think) told me how.
>>
>> Thinking later, I see that it is better, can't happen by accident, as
>> can happen to a push button.
>
>Indeed. I somehow accidentally paused my Ski Tracks app for 4 or 5 runs
>the other day, probably missing the ACTUAL top speed I hit -- I hope. I
>always blank the screen before putting it back in my pocket, so I don't
>see how I could have accidentally hit the pause icon, but it happened.

That sounds like a good idea. How do you blank the screen?

On Sun, 5 Feb 2023 22:41:03 +0100, "Carlos E.R."
<robin_listas@es.invalid> wrote:

>On 2023-02-05 22:24, The Real Bev wrote:
>> On 2/5/23 12:04 PM, Carlos E.R. wrote:
>>> On 2023-02-05 20:26, Ken Blake wrote:
>>
>>>> On my Android phone (Pixel 4a) I have to slide it up. To me, that's
>>>> very counterintuituve. I couldn't figure out how to do it until
>>>> someone here (Vanguard, I think) told me how.
>>>
>>> Thinking later, I see that it is better, can't happen by accident, as
>>> can happen to a push button.
>>
>> Indeed.  I somehow accidentally paused my Ski Tracks app for 4 or 5 runs
>> the other day, probably missing the ACTUAL top speed I hit -- I hope.  I
>> always blank the screen before putting it back in my pocket, so I don't
>> see how I could have accidentally hit the pause icon, but it happened.
>>
>>>>> It is obvious once you know it. Different user paradigm than a
>>>>> computer.
>>
>> Android apps are on the whole pretty intuitive -- a good thing, because
>> nobody can write instruction manuals any more.  If the authors would
>> just stop lying it would be a big step forward.
>
>They are intuitive, after the initial shock. Then yes, everything is
>intuitive.
>
>I know people that can't handle it, so for them it is not intuitive at
>all, and ask me how do I install Whatsapp, then how I open whatsapp. If
>the icon doesn't fit in the first "worskpace" and is in the second, they
>don't find it. Need to be told how to slide to the second space.
>
>>
>>>> It *is* a computer, as far as I'm concerned, just a very small one.
>>>> But yes, it's a very different user paradigm from a Windows computer,
>>>> and that's a good part of the reason I know relatively little about
>>>> it.
>>
>> Last time I used windows regularly was win95.  It was OK.  Then I
>> switched to slackware (always use the system your live-in help does).
>>
>>> I meant a "normal" computer :-D
>>
>> Linux, obviously.
>
>For me, yes, although I sometimes have to use Windows. Both are similar
>in the user interface: double click icons, mouse, etc. A "normal
>computer" in this context is a desktop computer, a laptop, running whatever.

Yes, "whatever" isn't the same for all of us. For me it's Windows, and
always has been since the days of MS-DOS.

On Sun, 5 Feb 2023 14:14:13 -0800, The Real Bev <bashley101@gmail.com>
wrote:

>On 2/5/23 1:41 PM, Carlos E.R. wrote:
>> On 2023-02-05 22:24, The Real Bev wrote:
>
>>> Last time I used windows regularly was win95.  It was OK.  Then I
>>> switched to slackware (always use the system your live-in help does).
>>>
>>>> I meant a "normal" computer :-D
>>>
>>> Linux, obviously.
>>
>> For me, yes, although I sometimes have to use Windows. Both are similar
>> in the user interface: double click icons, mouse, etc. A "normal
>> computer" in this context is a desktop computer, a laptop, running whatever.
>
>Something with a real keyboard -- one we can use with our eyes closed
>most of he time;

*You* can. Not me. I never learned to touch type.

> I never did learn to touch-type numbers and symbols.

On Sun, 5 Feb 2023 14:26:59 -0700, AJL <noemail@none.com> wrote:

>On 2/5/2023 1:36 PM, Ken Blake wrote:
>> On Sun, 5 Feb 2023 13:04:34 -0700, AJL <noemail@none.com> wrote:
>>> On 2/5/2023 12:26 PM, Ken Blake wrote:
>>>> On Sat, 4 Feb 2023 19:57:16 +0100, "Carlos E.R."
>
>>>>> I think I phoned back and asked my friend how the heck was I
>>>>> supposed to answer a call, if pressing the button doesn't work.
>>>>> "You have to slide it to the side". One side (red) to cancel,
>>>>> another (green) to accept.
>
>>>>> Argh.
>
>>>> On my Android phone (Pixel 4a) I have to slide it up. To me,
>>>> that's very counterintuituve. I couldn't figure out how to do it
>>>> until someone here (Vanguard, I think) told me how.
>
>>> On my phone (Galaxy S10+) there's a setting that when set allows
>>> me to answer the phone by simply pushing the up button on the case.
>>> I don't have to look at or touch the screen at all. Check yours,
>>> maybe you have such a setting. It's very handy, especially on the
>>> freeway... 8-O
>
>> Getting my phone out of my pocket while I'm driving would be a giant
>> problem for me.
>
>Time for a belt case.

I tried a couple a while back. They didn't work well for me.

Now that I wear suspenders instead of a belt, it would be even worse.

>My phone pops out easily no matter where I am. But
>the freeway thing was supposed to be a joke...note the emoticon...

Sorry, I missed it.

>> But my phone connects to my car via bluetooth, and it's very quick
>> and easy to answer it on the dashboard.
>
>Does your Bluetooth work in the grocery store? But never mind.

No, but it's easy to take out of my pocket standing up. It's sitting
in the car buckled up that makes it hard.

On Sun, 5 Feb 2023 13:17:06 -0800, The Real Bev <bashley101@gmail.com>
wrote:

>On 2/5/23 11:26 AM, Ken Blake wrote:
>> On Sat, 4 Feb 2023 19:57:16 +0100, "Carlos E.R."
>> <robin_listas@es.invalid> wrote:
>>>On 2023-02-04 18:59, The Real Bev wrote:
>>>> On 2/3/23 9:41 PM, Thomas wrote:
>>>>> On Saturday, February 4, 2023 at 3:03:01 AM, The Real Bev wrote:
>>>>>
>>>>>>  I see no need for a snotty response to a non-snotty message.
>>>>>
>>>>> Have you never seen what Ken Blake often posts or are you basing your
>>>>> assessment of his MENSA like genius on this one thread where he showed
>>>>> true
>>>>> talent for misunderstanding how to move icons on his phone's home screen.
>>>>
>>>> I don't read everything.  Ken Blake has been here for a long time and
>>>> has offered useful information.  Using software devised by others
>>>> frequently provides annoying surprises because we do not all think the
>>>> same way.  We have blind spots, which is why it's good to have
>>>> proofreading done by someone who didn't write the material.
>>>>
>>>> There ARE dumb questions, but there are more dumb answers.
>>>
>>>I have been using computers since maybe 1980, if one can consider a
>>>programmable calculator a computer (a TI 57 or 58). I did programming
>>>for a living for some time. Yet, when I bought my first Android smart
>>>phone, a Samsung Mini 2 (plus?), and got my first call, I was unable to
>>>answer it. Nothing worked.
>
>We got our first one in 1977. Hubby wrote assemblers and
>cross-assemblers for sale until the chip manufacturers figured they'd
>been missing out on a nice revenue source and wrote their own. I put
>dBaseII on it to do a project. Later on I took a FORTRAN course. I
>hate programming. REALLY hate it. I just don't think with the required
>granularity.

I haven't written a program in umpteen years, but back when I did it
regularly, I loved it.

I started with 1401 SPS, then Autocoder, then COBOL, and a little bit
of 7080 assembler and 360 assembler and this and that.

I've certainly forgotten a lot, but if I needed to, I could quickly
relearn any language I used to know.

>I eventually because what was known as a "power user". Not much money
>in that :-(
>
>> I've been using computers for 60 years--since 1962. I started working
>> as a programmer then and was a computer professional with various jobs
>> until I retired in 1993. These days, I know Windows well, and also
>> several programs (Microsoft and third-party) that run under it, but
>> what I still know the least about is how to use my Android smart
>> phone.
>>
>>>I think I phoned back and asked my friend how the heck was I supposed to
>>>answer a call, if pressing the button doesn't work. "You have to slide
>>>it to the side". One side (red) to cancel, another (green) to accept.
>
>That sounds very familiar :-( I can't remember how I learned about
>sliding, but I know I had to return the first half-dozen or so calls I
>received.
>
>>>Argh.
>>
>> On my Android phone (Pixel 4a) I have to slide it up. To me, that's
>> very counterintuituve. I couldn't figure out how to do it until
>> someone here (Vanguard, I think) told me how.
>>
>>>It is obvious once you know it. Different user paradigm than a computer.
>>
>> It *is* a computer, as far as I'm concerned, just a very small one.
>> But yes, it's a very different user paradigm from a Windows computer,
>> and that's a good part of the reason I know relatively little about
>> it.
>
>Mine is mostly a camera. A lot of the other quasi-useful functions just
>don't work as well as they should or throw up ads that make the app
>itself useless.

On 2/5/23 2:48 PM, Ken Blake wrote:
> On Sun, 5 Feb 2023 13:24:29 -0800, The Real Bev <bashley101@gmail.com>
> wrote:
>
>>On 2/5/23 12:04 PM, Carlos E.R. wrote:
>>> On 2023-02-05 20:26, Ken Blake wrote:
>>
>>>> On my Android phone (Pixel 4a) I have to slide it up. To me, that's
>>>> very counterintuituve. I couldn't figure out how to do it until
>>>> someone here (Vanguard, I think) told me how.
>>>
>>> Thinking later, I see that it is better, can't happen by accident, as
>>> can happen to a push button.
>>
>>Indeed. I somehow accidentally paused my Ski Tracks app for 4 or 5 runs
>>the other day, probably missing the ACTUAL top speed I hit -- I hope. I
>>always blank the screen before putting it back in my pocket, so I don't
>>see how I could have accidentally hit the pause icon, but it happened.
>
> That sounds like a good idea. How do you blank the screen?

Light press on the power button. I should just let it blank by itself;
the power switch on my Lenovo tablet has given up the ghost multiple
times (the youtube fix only works for a short time) and I don't want it
to happen to the phone, but I can't help myself -- I ALWAYS turn off
lights :-(

--
Cheers, Bev
I'd tell you a UDP joke, but you might not get it.
-- K.E. Long

On 2/5/23 2:51 PM, Ken Blake wrote:
> On Sun, 5 Feb 2023 14:14:13 -0800, The Real Bev <bashley101@gmail.com>
> wrote:
>
>>On 2/5/23 1:41 PM, Carlos E.R. wrote:
>>> On 2023-02-05 22:24, The Real Bev wrote:
>>
>>>> Last time I used windows regularly was win95.  It was OK.  Then I
>>>> switched to slackware (always use the system your live-in help does).
>>>>
>>>>> I meant a "normal" computer :-D
>>>>
>>>> Linux, obviously.
>>>
>>> For me, yes, although I sometimes have to use Windows. Both are similar
>>> in the user interface: double click icons, mouse, etc. A "normal
>>> computer" in this context is a desktop computer, a laptop, running whatever.
>>
>>Something with a real keyboard -- one we can use with our eyes closed
>>most of he time;
>
> *You* can. Not me. I never learned to touch type.

It was a requirement in jr. high. Everybody had to learn to type.
Everybody had to take shop. Everybody had to take home ec. I didn't
appreciate it at the time, but I do now. I made a wooden address board
in wood shop and learned to make fluffy omelets and shit on a shingle
(both were REALLY disgusting) in home ec. Typing was the most useful.

>> I never did learn to touch-type numbers and symbols.

They should have included those in the copy, but they didn't.

--
Cheers, Bev
I'd tell you a UDP joke, but you might not get it.
-- K.E. Long

On 5 Feb 2023 at 21:24:29, The Real Bev <bashley101@gmail.com> wrote:
> On 2/5/23 12:04 PM, Carlos E.R. wrote:
>> On 2023-02-05 20:26, Ken Blake wrote:
>
>>> On my Android phone (Pixel 4a) I have to slide it up. To me, that's
>>> very counterintuituve. I couldn't figure out how to do it until
>>> someone here (Vanguard, I think) told me how.
>>
>> Thinking later, I see that it is better, can't happen by accident, as
>> can happen to a push button.
>
> Indeed. I somehow accidentally paused my Ski Tracks app for 4 or 5 runs
> the other day, probably missing the ACTUAL top speed I hit -- I hope. I
> always blank the screen before putting it back in my pocket, so I don't
> see how I could have accidentally hit the pause icon, but it happened.
>
>>>> It is obvious once you know it. Different user paradigm than a computer.
>
> Android apps are on the whole pretty intuitive -- a good thing, because
> nobody can write instruction manuals any more. If the authors would
> just stop lying it would be a big step forward.
>
>>> It *is* a computer, as far as I'm concerned, just a very small one.
>>> But yes, it's a very different user paradigm from a Windows computer,
>>> and that's a good part of the reason I know relatively little about
>>> it.
>
> Last time I used windows regularly was win95. It was OK. Then I
> switched to slackware (always use the system your live-in help does).
>
>> I meant a "normal" computer :-D
>
> Linux, obviously.
>

A 'real' computer is a big mainframe - preferably running Linux.

On 2/5/23 11:07 PM, Bob Martin wrote:
> On 5 Feb 2023 at 21:24:29, The Real Bev <bashley101@gmail.com> wrote:
>> On 2/5/23 12:04 PM, Carlos E.R. wrote:
>>> On 2023-02-05 20:26, Ken Blake wrote:
>>
>>>> On my Android phone (Pixel 4a) I have to slide it up. To me, that's
>>>> very counterintuituve. I couldn't figure out how to do it until
>>>> someone here (Vanguard, I think) told me how.
>>>
>>> Thinking later, I see that it is better, can't happen by accident, as
>>> can happen to a push button.
>>
>> Indeed. I somehow accidentally paused my Ski Tracks app for 4 or 5 runs
>> the other day, probably missing the ACTUAL top speed I hit -- I hope. I
>> always blank the screen before putting it back in my pocket, so I don't
>> see how I could have accidentally hit the pause icon, but it happened.
>>
>>>>> It is obvious once you know it. Different user paradigm than a computer.
>>
>> Android apps are on the whole pretty intuitive -- a good thing, because
>> nobody can write instruction manuals any more. If the authors would
>> just stop lying it would be a big step forward.
>>
>>>> It *is* a computer, as far as I'm concerned, just a very small one.
>>>> But yes, it's a very different user paradigm from a Windows computer,
>>>> and that's a good part of the reason I know relatively little about
>>>> it.
>>
>> Last time I used windows regularly was win95. It was OK. Then I
>> switched to slackware (always use the system your live-in help does).
>>
>>> I meant a "normal" computer :-D
>>
>> Linux, obviously.
>
> A 'real' computer is a big mainframe - preferably running Linux.

Our desktops are more powerful than the mainframes of the 60s. Some say
our phones are too.

--
Cheers, Bev
"By the time they had diminished from 50 to 8, the other
dwarves began to suspect 'Hungry.'" -Gary Larson

Ken Blake wrote:

> Getting my phone out of my pocket while I'm driving would be a giant
> problem for me.

It would be illegal to even touch the phone here.

> But my phone connects to my car via bluetooth, and
> it's very quick and easy to answer it on the dashboard.

Or the steering wheel.

On 6 Feb 2023 at 07:49:59, The Real Bev <bashley101@gmail.com> wrote:
> On 2/5/23 11:07 PM, Bob Martin wrote:
>> On 5 Feb 2023 at 21:24:29, The Real Bev <bashley101@gmail.com> wrote:
>>> On 2/5/23 12:04 PM, Carlos E.R. wrote:
>>>> On 2023-02-05 20:26, Ken Blake wrote:
>>>
>>>>> On my Android phone (Pixel 4a) I have to slide it up. To me, that's
>>>>> very counterintuituve. I couldn't figure out how to do it until
>>>>> someone here (Vanguard, I think) told me how.
>>>>
>>>> Thinking later, I see that it is better, can't happen by accident, as
>>>> can happen to a push button.
>>>
>>> Indeed. I somehow accidentally paused my Ski Tracks app for 4 or 5 runs
>>> the other day, probably missing the ACTUAL top speed I hit -- I hope. I
>>> always blank the screen before putting it back in my pocket, so I don't
>>> see how I could have accidentally hit the pause icon, but it happened.
>>>
>>>>>> It is obvious once you know it. Different user paradigm than a computer.
>>>
>>> Android apps are on the whole pretty intuitive -- a good thing, because
>>> nobody can write instruction manuals any more. If the authors would
>>> just stop lying it would be a big step forward.
>>>
>>>>> It *is* a computer, as far as I'm concerned, just a very small one.
>>>>> But yes, it's a very different user paradigm from a Windows computer,
>>>>> and that's a good part of the reason I know relatively little about
>>>>> it.
>>>
>>> Last time I used windows regularly was win95. It was OK. Then I
>>> switched to slackware (always use the system your live-in help does).
>>>
>>>> I meant a "normal" computer :-D
>>>
>>> Linux, obviously.
>>
>> A 'real' computer is a big mainframe - preferably running Linux.
>
> Our desktops are more powerful than the mainframes of the 60s. Some say
> our phones are too.

Yes, but check out a modern mainframe, that's where your bank account is.
Over a trillion transactions per day.

On Sun, 5 Feb 2023 21:24:14 -0800, The Real Bev <bashley101@gmail.com>
wrote:

>On 2/5/23 2:51 PM, Ken Blake wrote:
>> On Sun, 5 Feb 2023 14:14:13 -0800, The Real Bev <bashley101@gmail.com>
>> wrote:
>>
>>>On 2/5/23 1:41 PM, Carlos E.R. wrote:
>>>> On 2023-02-05 22:24, The Real Bev wrote:
>>>
>>>>> Last time I used windows regularly was win95.  It was OK.  Then I
>>>>> switched to slackware (always use the system your live-in help does).
>>>>>
>>>>>> I meant a "normal" computer :-D
>>>>>
>>>>> Linux, obviously.
>>>>
>>>> For me, yes, although I sometimes have to use Windows. Both are similar
>>>> in the user interface: double click icons, mouse, etc. A "normal
>>>> computer" in this context is a desktop computer, a laptop, running whatever.
>>>
>>>Something with a real keyboard -- one we can use with our eyes closed
>>>most of he time;
>>
>> *You* can. Not me. I never learned to touch type.
>
>It was a requirement in jr. high. Everybody had to learn to type.
>Everybody had to take shop. Everybody had to take home ec.

I'm 85, probably significantly older than you. When I was in school,
girls leaned to type, boys took shop.

>I didn't
>appreciate it at the time, but I do now.

I wish i had learned.

I made a wooden address board
>in wood shop and learned to make fluffy omelets and shit on a shingle
>(both were REALLY disgusting) in home ec. Typing was the most useful.
>
>>> I never did learn to touch-type numbers and symbols.
>
>They should have included those in the copy, but they didn't.

On Sun, 5 Feb 2023 21:18:59 -0800, The Real Bev <bashley101@gmail.com>
wrote:

>On 2/5/23 2:48 PM, Ken Blake wrote:
>> On Sun, 5 Feb 2023 13:24:29 -0800, The Real Bev <bashley101@gmail.com>
>> wrote:
>>
>>>On 2/5/23 12:04 PM, Carlos E.R. wrote:
>>>> On 2023-02-05 20:26, Ken Blake wrote:
>>>
>>>>> On my Android phone (Pixel 4a) I have to slide it up. To me, that's
>>>>> very counterintuituve. I couldn't figure out how to do it until
>>>>> someone here (Vanguard, I think) told me how.
>>>>
>>>> Thinking later, I see that it is better, can't happen by accident, as
>>>> can happen to a push button.
>>>
>>>Indeed. I somehow accidentally paused my Ski Tracks app for 4 or 5 runs
>>>the other day, probably missing the ACTUAL top speed I hit -- I hope. I
>>>always blank the screen before putting it back in my pocket, so I don't
>>>see how I could have accidentally hit the pause icon, but it happened.
>>
>> That sounds like a good idea. How do you blank the screen?
>
>Light press on the power button.

Thanks. I'll try that.

I should just let it blank by itself;
>the power switch on my Lenovo tablet has given up the ghost multiple
>times (the youtube fix only works for a short time) and I don't want it
>to happen to the phone, but I can't help myself -- I ALWAYS turn off
>lights :-(

On 6 Feb 2023 07:07:06 GMT, Bob Martin <bob.martin@excite.com> wrote:

>On 5 Feb 2023 at 21:24:29, The Real Bev <bashley101@gmail.com> wrote:
>> On 2/5/23 12:04 PM, Carlos E.R. wrote:
>>> On 2023-02-05 20:26, Ken Blake wrote:
>>
>>>> On my Android phone (Pixel 4a) I have to slide it up. To me, that's
>>>> very counterintuituve. I couldn't figure out how to do it until
>>>> someone here (Vanguard, I think) told me how.
>>>
>>> Thinking later, I see that it is better, can't happen by accident, as
>>> can happen to a push button.
>>
>> Indeed. I somehow accidentally paused my Ski Tracks app for 4 or 5 runs
>> the other day, probably missing the ACTUAL top speed I hit -- I hope. I
>> always blank the screen before putting it back in my pocket, so I don't
>> see how I could have accidentally hit the pause icon, but it happened.
>>
>>>>> It is obvious once you know it. Different user paradigm than a computer.
>>
>> Android apps are on the whole pretty intuitive -- a good thing, because
>> nobody can write instruction manuals any more. If the authors would
>> just stop lying it would be a big step forward.
>>
>>>> It *is* a computer, as far as I'm concerned, just a very small one.
>>>> But yes, it's a very different user paradigm from a Windows computer,
>>>> and that's a good part of the reason I know relatively little about
>>>> it.
>>
>> Last time I used windows regularly was win95. It was OK. Then I
>> switched to slackware (always use the system your live-in help does).
>>
>>> I meant a "normal" computer :-D
>>
>> Linux, obviously.
>>
>
>A 'real' computer is a big mainframe - preferably running Linux.

I worked on mainframes both big and small for many years, but I
haven't seen one in 30 years. Can mainframes run Linux? I thought they
could run Unix, but not Linux.

On Mon, 6 Feb 2023 14:05:09 +0000, Andy Burns <usenet@andyburns.uk>
wrote:

>Ken Blake wrote:
>
>> Getting my phone out of my pocket while I'm driving would be a giant
>> problem for me.
>
>It would be illegal to even touch the phone here.
>
>> But my phone connects to my car via bluetooth, and
>> it's very quick and easy to answer it on the dashboard.
>
>Or the steering wheel.

Maybe. I'm not sure about my car.