Wednesday, July 19, 2017
Wednesday, July 12, 2017
I am writing a calendar app that will listen for clicks on dates and drive the remainder of the app's functions by date and user.
The reason I am posting this is that my fragments replaced the main activity okay on a Lollipop device, but not on Marshmallow
After many hours of frustration, I happened to tilt the Marshmallow phone just enough to have the external light source reveal that the fragment was indeed present on the main activity, but BEHIND IT. This was not readily detected because the backgrounds are the same color and size while the main activity layout was 100% opaque. It was my elevation shadow that showed another layer beneath the main activity
Shazam!!! This fixed that problem:
This may not be proper form, but I don't care as I must push on and build the server application to the mobile. Meanwhile, here are some screen shots of the actual source code that I built and compiled directly on a Samsung Tablet with AIDE.
Aha...the all important build.gradle file
Saturday, July 8, 2017
I started by reading the AWS documentation.
Get AWS account and create and Windows Server Instance - Already plenty of on-line documentation.
Saturday, July 1, 2017
RESOLUTION: Use the CORRECT constructor for ActionBarDrawerToggle:
ActionBarDrawerToggle (Activity activity,
Toolbar toolbar, ◄ - THIS IS THE KEY. Previously missing.
The main activity should extend AppCompatActivity.
and create an instance of android.support.v7.widget.Toolbar
There are plenty of full code examples online but remember to setSupportActionBar(toolbar); and that is it!
Here is what my build.gradle looks like:...