New
Thank you again for your replies,
but at this point I just want to see what the B4A documentation says about styles/Themes.. can you please point me to that specific documentation?
:sign0163:
I was interested in using the processes outlined in the link I attached previously, but,,,,, as my form -- image attached in earlier post.... shows,,,
I will have several areas that existed in the original app as custom user controls and each has their own specific styling. Text size color etc,,
I am attempting to replicate this windows based UI in Android..
Apparently this cannot be done with the processes described in my earlier attached link.
These processes can be applied to individual views by type,
all labels or all textedits or all buttons....
or to an entire activity by name, (this "applied to activity by name process" although I have not seen exemplified correctly, I am interested in understanding it) So each activity could have specific styling..
Since I use a "panel" as a container to "house" if you will,,, what I refer to as a user control" (which is really just a collection of views)
if I could apply a style to a panel and of course all of its ""Children"" this would address my needs..
:BangHead::BangHead:
the labels that exist as children to panelOrderBins could all have blue 25pt text, while all the labels for panelHeader could have 20pt white text with the exception of the odd one that I designate in code to be a larger Font...
That last condition, for the odd exception isn't even possible using styles.. that I'm aware of
So instead of being as customizable as a web based CSS file it seems more pointless than helpful for my immediate needs. With CSS I could name the panel that houses my views and apply a style. I could then name the odd man out in that panel that breaks the normal standard and by name in the CSS specify his exceptions Big Red Text whatever... Its like someone said already.. 85-90 percent of my development in B4A ends up as ugly UI contortions
I figured out the hierarchy for styles and themes --- you call out a theme and override its subcategories with specific styles in another xml file just like the theme xml file -- I thought this extra indirection was pointless and difficult to understand myself as it took me longer than necessary to grasp it, because of this added yet unrequited indirection. It works with just a style file and not theme prefixing it...
:sign0163: