Thank you for your input. My own world championship is to just get through life with as few seizures(Epilepsy) as possible and be Happy.
Maybe you already know that, but in France, two researchers made recently a major breakthrough concerning epilepsy. Here's an article in french:
http://www.laprovence.com/article/a...eille-ils-ont-mis-lepilepsie-en-equation.html
An abstract in english of their scientific paper:
http://www.ncbi.nlm.nih.gov/pubmed/24919973
Understand Arrays - my weakest link
What exactly don't you understand about arrays?
Arrays can be seen as isolated memory cells (what's in a cell don't affect any other cell). If you declare an array like this: Dim Numbers(100) As Int, then you have one hundreds integers that you can set like this:
Numbers(4) = 6 (you store 6 in the fifth cell of your array)
If Numbers(3) = 400 then ... (if the 4th number of your array is 400 then ...)
Note that the index of the array starts at 0 so the first cell has the index 0, the second cell 1, etc.
You can have arrays of anything, e.g. Dim MyEditTexts(5) As EditText.
If you have many views of the same type in the same activity, it's often more convenient to declare them as an array because you can use a loop to initialize them, to change their properties, to store their contents in a database, etc. Example:
For e = 0 to 4
EditText(e).Text = ""
Next
designing without Designer - don't think I'll ever get this one
Each view that you create in the designer generates a code like this:
Dim MyView As ViewType
MyView.Initialize(....)
MyView.Property1 = ...
MyView.Property2 = ...
Activity.AddView(MyView, X, Y, Width, Height)
Thus, to create a view outside the designer, you just have to do the same thing. A real example with a label:
Dim MyLabel As Label
MyLabel.Initialize("MyEventPrefix")
MyLabel.TextSize = 24
MyLabel.Text = "My label text"
Activity.AddView(MyLabel, 20dip, 20dip, 100dip, 25dip)
My main problem is I just don't have enough time to sit down and concentrate on what I am doing
Then proceed step by step. You don't need to sit for hours to learn how arrays work. And you can try to focus on a smaller part of the problem to solve. For example, in my job (I manage servers), when the servers have no failure (which unfortunately is uncommon when you have 400 servers), I have nothing to do and it's the opportunity to write messages like this one. So my working hours are very fragmented and I have a clear idea of what can be a day when you're frequently interrupted and cannot do something that lasts. It's not always compatible with programming (and I have to write code in my job). So I have to follow one direction and only one; when I've done with it, I follow another one, and so on. I cannot try to change something here, then something there, fix this part, add this missing class, etc. or I'll be completely lost. There's no other advice that can be given in your case. Don't try to learn everything at once. Select only one goal for now. As english people says: "Jack of all trades, master of none".
