From: Panayotis K. <pan...@pa...> - 2009-10-11 09:55:07
|
On 11 Οκτ 2009, at 10:05 π.μ., Wolfgang Korn wrote: > The only features a UIButton supports right now is creation, setting > its > title and to register an event handler. Especially all the color stuff > you mentioned is currently not supported. What you saw in the Java > version of UIButton (these methods based on java.awt.Color) are only > used inside our Java emulator to create a UIAlertView with properly > colored buttons. This Java implementation should be fixed as soon as > we > support color operations based in UIColor. And thanks for mentioning > the > UIButtonTest. Since this uses the java.awt.Color based methods it > cannot > be cross-compiled. I think we should remove that from the repository > to > avoid confusion. > > Coming to the String question. I lately noticed that the > java_lang_String implementation is based on NSMutableString. This > should > be fixed since in Java strings are immutable. That's one thing I > have on > my list - but not with highest priority. > So, for example I found that the UIControlEventValueChanged is not understood in the simulator, while it is perfectly understood in the native application. In order to implement things like that in the emulator, is something like this patch appropriate? it still has some issues but I just want to understand the main idea. In order to catch more than one of these events, should I double the request like here, or I can do something like ( UIControlEventTouchUpInside | UIControlEventValueChanged ) |