dgets / dton Goto Github PK

As mentioned in #8, the RecyclerView is currently just scrolling items off of the screen instead of letting us scroll through them in any sort of vertical manner. Need to fix this and make sure that other layout such as anchoring and constraints are set properly.

Just a brief synopsis of the goals of this project will suffice for now.

This is really necessary at this point. We're going to be handling a lot of testing through the coming iterations, and having to manually deal with that god-awful android emulator mouse point 'n click interface with each time that a new run occurs would take more time than doing the hacking itself. So before anything else, I think it's important to get that list save working and autoloading, so that we can jump right into whatever we need to test upon an iteration instead of fumbling with that crap.

For example, in the primary display, the frequency box is currently populated initially with the resource identifier @numeric/base_frequency, instead of the corresponding resource's value. There is a good reason to have some numerics pre-populated here, so it'd be good to get this figured out.

After something such as presets being loaded initially occurs, the entire list is appended to what is already there if you do anything that requires another call to updateDisplay(). Thus, the method needs to wipe its contents before adding whatever needs to be in there after whatever action was taken.

This may actually require shifting the layout to contain a different sort of element than the TableRow that they're currently within. I have no idea if this has an _onClick method, or anything similar, but I'll be digging through the methods soon here.

Either way, we need to figure out when a user has clicked one of the entries, no matter what thread it requires us to follow.

Check through the layout and xml for the warnings regarding unanchored elements that will float upon resizing. Read the dox on the different forms of anchoring, too, so that things don't become such a mess when the onscreen keyboard is active.

I'm thinking right now that checking for a long click, then displaying a confirmation dialog, is probably the best way to go about this. Hopefully the TextView will implement such without any sort of godawful headaches like implementing onClick() for the RecyclerView/CardView layout that I had before.

With commit 7485b5f, playback and stopping playback for a single tone is working without any issues. However, due to the asynchronous nature of things, it is possible to play back more than one tone at a time. When this happens, clicking the associated preset list item to try to stop the tone will only end a single tone. Multiple clicks to the other entries will start playback for more, but you cannot end the playback of other concurrent tones; at least not all of them. This needs to be fixed; unless, due to the way things are set up, it turns into a nightmare, in which case it might be easier to just limit playbacks to one tone at a time until I've gotten through enough Android and Java classes/tutorials to be able to handle this the right way.

There's some inline documentation, but none of the actual javadoc. Get it added.

Put these into the resources, where they belong.

This leaves the text notice for what goes into that field needing to be manually deleted. I think there were some issues with saving the name for the particular preset frequency, as well, but I do know that sometimes that one works.

• fix click into and out of (restore the message if nothing else there) the preset frequency entry name field
• fix the same for the preset frequency entry frequency field

If nothing else, at least for wrappers to Toast for debugging; the constants can probably be moved into this section, as well, since they are in an ill-named class at the moment.

Perhaps not worthy of a full issue, but I'm doing it so that I have the notes somewhere on any issues that might arise with dynamic addition of entries to a TableLayout. Things seem to be going good (at least as far as programmatic static entry to the table), but I know I've run into issues when I've tried any layout with this complex of a structure before. Remember, I'm not a total 'droid virgin, but my layout skills leave quite a bit to be desired at this point.