Arlen_Holder
news alt.comp.freeware, wrote:

On Sat, 10 Nov 2018 03:24:33 -0000 (UTC), Diesel wrote:

I believe that you're so arrogant that you feel as if it's never
necessary to read the instructions, or even give them so much as
a glance over before you jump right in, expecting excellent
results, on the first attempt.

Hi Diesel,
Thanks for your kind advice where you are far more experienced
than I. I'm a noob. I never said I wasn't a noob. So let's be
clear: I'm a noob.

You keep changing your position on that, Arlen. It's the second time
you've admitted that you're nowhere near me in so far as skillset
and/or knowledge is concerned, yet you tried to mock me (again) with
a reply to another poster...I know you're in no position to do that
and be able to back any of it up, but, I enjoy reminding you of your
dishonesty, since you like to claim you only deal in facts. Clearly,
you don't.

Unfortunately, since I have an old AMD-based Windows desktop, I
have been successful using the Microsoft Android Emulator, which
is working astoundingly perfectly, which allows me to test any
Android phone or tablet that I want to test with any Android API.

You chose to purchase a piece of **** without knowing what was under
the hood. Like so many (Don't get me wrong, I make good money
repairing name brand junk) others who are brand loyal. All of that
aside, Your AMD powered machine most certainly can run Android
emulators and various other kinds of emulation, should you so desire.
I have a single remaining Much older than yours AMD machine here.
I've already performed various tests with it, attempting to duplicate
the issue you were experiencing previously.

I wasn't able to duplicate the issue you experienced because unlike
you, I know what the machine is and configured it beforehand.
Something you didn't do, for atleast twenty! reinstallations that you
yourself admit to having to do. That's alot of reinstalls and time
wasted because you didn't understand what your machine was on the
hardware level and let's be honest, Arlen, didn't have a clue what
you were attempting to do.

You've managed to do a bit of fishing though with the thread and have
succesfully reeled in one person who's willing to ignore what many
others have written concerning you (along with what I've written) and
proceed to disregard all of that (including taking all of this
nonsense to email) and exchange 'programming 101' tips with you here.
So, I congratulate you for that, and to answer another posters
question, yes, there's enough suckers that you won't exhaust the
supply anytime soon.

The registry fix I suggested for you still applies, and, I'd
still advise for you and Bill to properly create it.

Thanks for your advice on that registry fix.

Which you've prompty disregarded for the second or third time now.
It's probably just as well since you demonstrated a clear inability
to follow very simple directions and weren't able to create the key
with the proper setting anyway.

All the documentation you referenced (which I saw also of course),
was with respect to getting the Visual Studio to work with the
Microsoft Android Emulator.

Some of what you're calling documentation is from my own notes which
haven't been published to the internet, so, contrary to what you've
written (you lied again, Arlen) you haven't 'also seen it'.

None of that documentation was for getting the Android Emulator to
work with Android Studio, AFAIK.

As I said, I don't know what documentation you're specifically
referencing and I'm not all that interested in arguing with a n00b
who can't set a simple registry key why they should have done so, but
I'm not going to spend alot of time trying to convince you to set the
key, either. if you feel you don't need it, and have already shown
you don't know how to work with the system registry, that's okay with
me. From my pov, everything looks great from my house.

A computer is a very
complex piece of machinery; the software is yet another layer of
complexity.

The good news is that I've figured out, today, how to copy a
project, which, if anyone here has ever tried it, is _not_
intuitive.

Actually, you're wrong (again). It's not a difficult thing to do for
anyone who has programming experience under their belt, and, I'm not
talking about his/her first virgin breaking hello world job, either.

For crying out loud, you're working with a script based language. You
aren't doing any serious 'coding' on your own here.

In fact, just like everyone with older AMD had problems
getting the Google emulators to work, everyone who copies a
project has problems getting Android Studio to _recognize_ that
copied project.

There's no such fact. Not everyone had problems getting the emulators
to work on an AMD based system. The ONLY people who had trouble
getting it up and running from what I read are those who didn't know
what the hardware was and so, didn't set it up properly to run the
emulation software they elected to play with. Don't assume 'everyone
with older AMDs' had problems when infact, not everyone did.

People like you did, but, people like you, thankfully, are not
everyone.

It took a few hours, but I got further than most people who just
gave up.

It took more than a few hours, Arlen. There's no need for you to be
that dishonest. Naturally, you got further than anyone who gave up;
because (drum roll) they gave up. Had they bothered to do a little
more digging, they would have gotten it up and running too.

It's just as well they gave up on such a simple process as they would
have made for rather lousy programmers since they couldn't solve a
relatively simple (contrary to what you've claimed repeatedly) issue
of emulator installation and proper configuration.

The reason a copy of a project is important is for these
multi-step tutorials, at the end of one 5-part tutorial, you have
app03, for example, which is the beginning of part two.

Arlen, I have alot more experience writing code for the masses than
you do, so, I don't require a history lesson in why you'd be doing
what you are doing now. It's NOT NEW to me. I've been doing this for
years. It's not exclusive to Android or any particular programming
environment either, it's just good coding practice.

Well - you don't know how complex that turns out to be until
you've done it!

Come back to me with how complex something turns out being when
you're looking at hundreds of thousands of lines of code in the main
project source and several thousands of lines of code in each
external module that was compiled seperatly but will become part of
the main program as part of the compiling process on the main source
code. When you've written apps like that, then you can make
suggestions on how to improve the process and/or claim (rightfully)
how complicated the process can be.

As it is right now though, you aren't doing anything complicated to
anyone with a programming background. You're a n00bie taking baby
steps. And, instead of taking selfies for attention like an attention
starved teenager, you're wasting peoples time on usenet with stupid
threads like this one. End result for you is the same, attention
cravings satisfied.

In 20/20 hindsight, you might not want to even _think_
about it, but I didn't know that when I first tried it.
But I was just now completely successful in doing that simple task
(which almost nobody knows how to do, it turns out).

almost nobody who Arlen? Other n00bs to the world of coding like
yourself?

For Bill, and for the tribal record, if anyone is interested in

Why not just initiate the rest of this nonsense with Bill via email?
Or perhaps realtime via irc? There's no need for you to share
hundreds of lines of text to describe something to one individual who
has taken interest in what you're doing. Nobody else seems to be
interested in your troubles or boring diary/journal of your
failures/suggestions based on ignorance, etc.

for the first time now ... so as I copy more and more projects,
I'll hone it down to the steps that it needs to be.

Jesus, please, don't.

Needless to say, nobody on this planet knows of Google
documentation on this topic - which is sorely needed - as it's not
unheard of to want to copy app03 to app04 and have it work as
app04, particularly when you're learning, as I am...

What you're reinventing yet again Arlen is old hat, and old news to
people who actually have a programming background that they've stuck
with. IE: didn't have a passing interest for work related only like
you did.

================================================== =================
======== The next time I try this, I'll try to streamline the
steps so that everyone else will benefit from the time and energy
I spent on this to document it thoroughly.

Who's everyone Arlen? Why do you continue to avoid that question and
the majority of questions I ask of you? I can't help but notice you
tend to avoid questions presented by other posters as well. That's
not a very professional stance to take, Arlen. Especially when you
consider that you're essentially flooding somewhat various newsgroups
with crossposted threads you've created for your own personal
benefit; if you can catch a fish willing to help you.

And that's exactly what you're doing with this thread and the
previous ones.




--
To prevent yourself from being a victim of cyber
stalking, it's highly recommended you visit he
https://tekrider.net/pages/david-brooks-stalker.php
================================================== =
I tried being reasonable once. I didn't like it.