On Fri, 16 Nov 2018 00:19:17 +0000, Bill wrote:

It's hard to believe, but there was another MS update last night

Oh my... I'm sorry for you... that update is a killer sometimes.

I have a relatively recent thread on the Windows 10 ng on how to _prevent_
all MS updates from happening. I was successful at preventing updates for
_years_, for example, until the Microsoft update around the late January
time frame _bricked_ my system.

It's a loooooooong well documented saga, where I even resorted to taking
the desktop to the huge Microsoft Store (right across from the huge Apple
Store in the local San Jose Valley Fair shopping mall) - and after two or
three days - they declared that they couldn't unbrick it either. Sigh.

At that point, I gave up on stopping Microsoft updates.... but then ... a
month or two later ... I tried to completely remove Cortana (and not just
to redirect it to a dead browser)... which I was successful at actually ...
until the next Microsoft Update, which, ... guess what ... bricked my
system again. Again the Microsoft Store couldn't unbrick it.

Guess what I do now?
(HINT: My Windows is 100% up to date, & it has that stupid Cortana.)

Zipping everything up is probably a good plan.

Yep. In Windows, you can sequentially zip to app07_a.zip, app07_b.zip,
app07_c.zip, etc., and you always have a convenient "restore" point.

You can even zip to video tutorial time points, e.g.,
tutorial07_time15:45.zip, tutorial07_time20:30.zip, etc.

I'm not sure if you need to "Close" the Android project and to kill Android
Studio, but just in case there are files in a semi-accessible state (e.g.,
those in virtual memory?), I generally do the following before zipping:
1. AndroidStudio321:File Save All
2. AndroidStudio321:File Close Project
3. (I "x" out the project in the "Welcome Screen" that results)
4. AndroidStudio321:File Exit

I was surprised to see litres
in your list, it's a mess over here with litres, pounds, pints,
kilograms, feet, metres all mixed up.

Yup. Standard USA tire sizes, for example, are in inches (for the
diameter), millimeters (for the width), and percentages (for the height),
where I'm not sure how folks across the pond do tire sizes.

While everyone in the USA has duplicate sets of Imperial and Metric
wrenches, you UK folks have additional UK-specific sizes.

Most (if not all) of our liquids, solids, and gases (are there gases?) in
the grocery store, are in both Imperial and Metric quantities.

It's just our roads that are exclusively in Imperial units. They went to
metric before OPEC got mad at us in the 70s, but we pulled down all the
duplicated kilometer signs soon thereafter (in protest?).

While tools and groceries are dual-Imperial/Metric, I haven't seen a
kilometer road sign since the 70s.

My wife doesn't drive, so I sit outside the stores waiting while she
gabs to all her friends. That's when I try to re-grasp Java from my
ancient book.

Out here, everyone drives. You can't survive without driving.
We haven't even invented a school bus in California.
Nor mass transit that actually goes anywhere you need to go.

I live in mountains above Silicon Valley where the roads are single lane
for miles and miles and miles. We're so far from anything that I stock my
own gasoline, for example, where I always keep 50 gallons on hand for
refueling (since the nearest gas station is a 30 mile round trip).

Likewise with groceries. We stock fifty-pound bags of sugar and flour and
rice from Costco. Unfortunately, pasta only comes in puny six-pound packs
but olive oil, conveniently, comes in four-liter and one-liter packages.

I think it would be fun to write a Costco-specific grocery app, since
Costco has good prices on large quantities ... where they don't allow
picture taking but I do it anyway (and where I write on the labels in
pencil the price per unit since they conveniently are haphazard about
that).

One app that would be nice is a grocery store price comparison app.

I covered them in gory detail in 2014, but I haven't visited them since.
Comparing prices for grocery shopping using Android free app (9/19/2014)
https://groups.google.com/d/msg/comp.mobile.android/OlycIR5kIp8/cNmdPt0wD0MJ

The trick is populating a price database for each store where shopping
comparisons for just the items you care about can be compared at home.

So, I've now completed Butterfield 3, and am thinking about what to do
next while I try to vaguely understand what I have done. I will watch
the 4th video and think about that and whether it as worth going through
it as is or thinking of some other way to move on.

**Kudos to you for completing Butterfield 3!**

I hope my text posts helped.
If not, let me know as it's a LOT of work to post that stuff.
(I post it to be helpful - but if it's not helpful - then I can save the
effort and spend it on learning more instead of posting more.)

BTW, moving forward, here are the short "timer" videos I'm evaluating...

*Android alarm clock tutorial, by Anna Xu, published Jan 18, 2016*
o Part 1: Demo and user interface https://youtu.be/xbBlzOblD10
o Part 2: Initializing UI https://youtu.be/XIPSCe-38fM
o Part 3: The onClickListener https://youtu.be/KseXIsTLXaY
o Part 4: Alarm Manager https://youtu.be/R3AzhgzbpTc
o Part 5: Ringtone Service I https://youtu.be/GlLafRXJmGA
o Part 6: Ringtone Service II https://youtu.be/UDVfJzWpuWc
o Part 7: Ringtone Service III https://youtu.be/UCYv-TfKRMw
o Part 8: Notifications https://youtu.be/mgp7qjTXW2o
o Part 9: Spinner I https://youtu.be/eNZwsPEgVQI
o Part 10: Spinner II https://youtu.be/eNZwsPEgVQI
o Part 11: Spinner III https://youtu.be/TyFmKvvt3Zs

Now that I gave up on the SQL endeavor (for now), today I downloaded
that set of Anna Xu videos to start the evaluation on the first one.

I'll report back when/if I have something of value to report
(as I'm all about "adding value" in every post, if possible).

Moving around the ide is, as you say, getting smoother and somewhat more
familiar. I do feel I need to get a grip on Java and more au fait with
where to find things asap.

I agree on both points.

The IDE is happening as we inevitably get more comfortable with the IDE.
The java comprehension will happen as we inevitably need to debug errors.