android - AppCompat v22.1.0 not theming all xml widgets correctly for fragments -

-

when using xml based layouts using appcompat 22.1.0 not supported widgets tinted or material themed fragments using android 4.4.

i see behavior following widgets (others not tested):

  • radiobutton (no tint color)
  • checkbox (no tint color)
  • spinner (device default theme applied)
  • edittext (device default theme applied)
  • ratingbar (device default theme applied)
  • button (device default theme applied)

it used work in appcompat v22.0.0.

screenshot (left 4.4, right 5.0):

example screenshot

mainactivity.java:

public class mainactivity extends appcompatactivity {      @override     protected void oncreate(bundle savedinstancestate) {         super.oncreate(savedinstancestate);         setcontentview(r.layout.activity_main);         if (savedinstancestate == null) {             getsupportfragmentmanager()                     .begintransaction()                     .add(r.id.container, new placeholderfragment())                     .commit();         }     }      public static class placeholderfragment extends fragment {          public placeholderfragment() {         }          @override         public view oncreateview(layoutinflater inflater, viewgroup container, bundle savedinstancestate) {             view rootview = inflater.inflate(r.layout.fragment_main, container, false);             return rootview;         }     } }

fragment_main.xml

<linearlayout xmlns:android="http://schemas.android.com/apk/res/android"               android:layout_width="match_parent"               android:layout_height="match_parent"               android:orientation="vertical">      <radiobutton         android:layout_width="wrap_content"         android:layout_height="wrap_content"         android:checked="true"         android:text="radiobutton test"/>      <checkbox         android:layout_width="wrap_content"         android:layout_height="wrap_content"         android:checked="true"         android:text="checkbox test"/>      <spinner         android:layout_width="match_parent"         android:layout_height="wrap_content"         android:entries="@array/somestrings"/> </linearlayout>

themes.xml

<resources>     <style name="apptheme" parent="theme.appcompat.light.darkactionbar"></style> </resources>

this reported bug: https://code.google.com/p/android/issues/detail?id=169760

a temporary workaround use fragment parent activity layoutinflater: getactivity().getlayoutinflater() instead of supplied layoutinflater in oncreateview method.

example:

@override public view oncreateview(layoutinflater inflater, viewgroup container, bundle savedinstancestate) {     view rootview = getactivity().getlayoutinflater().inflate(r.layout.fragment_main, container, false);     return rootview; }

note: solution use special appcompat widgets in xml layout:

  • android.support.v7.widget.appcompatradiobutton
  • android.support.v7.widget.appcompatcheckbox
  • android.support.v7.widget.appcompatspinner

but mean need replace every single widget appcompat one.


Comments

Post a Comment

Popular posts from this blog

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall
Read more

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co
Read more

java - UML - How would you draw a try catch in a sequence diagram? -

-
Image
is there standard way of drawing try catch sequence diagrams? i've made attempt based on this feel end result doesn't feel right. code diagram based around: public static void save () { try { filehandle filehandle = gdx.files.external(file); filehandle.writestring(boolean.tostring(constantshandler.soundenabled)+"\n", false); (int = 0; < 5; i++) { filehandle.writestring(integer.tostring(constantshandler.highscores[i])+"\n", true); } } catch (throwable e) { } } my attempt note: know still need add loop. that's ok. fragments meant show conditional control flow in sequence diagram. superstructures puts limitations on use of fragments (see pp. 467 of ss2.1.1). should use critical region try part above. , option catch . however, keep telling can take quite freedom in using uml. it's language , such changes in life time. long reader ge
Read more