Is there any change in CN1 default theme?
Here is my form what it was looking prior on the phone
(it has list item background and square button by default)
Then all of a sudden from last 2 days, without changing anything in themes.res from my side, list item background and button shape have disappeared & button caption became all caps. As per this
This happened across the whole app and all of my 4 apps. Please may I know is the change going to be revert from the CN1 side or this is an enhancement?
I think it's explained in this blog post:
https://www.codenameone.com/blog/pixel-perfect-material-buttons.html
Related
Not entirely sure the best way to describe this strange behavior that I've been dealing with, so I've added screenshots below. Anyway, I've built portals inside of a tab control field on my layout. Initially, my fields inside of the portal would turn fully black whenever I scrolled through the records or tried to make edits to the field itself. However, after changing from the Classic Theme the file is currently using, it's stopped completely filling in black, but the fields are still showing some strange behavior.
Basically, even though I've made sure every possible alteration of the field (active, in focus, hover, etc) all have the exact same styling on them, the entire set of fields get this weird outline on them when I go to edit a single field.
Nothing selected here, this is how I'd like the portal to stay whether someone is making changes or not.
The "NRG" field is selected to make changes, and every other field ends up getting a strange border around the field.
Any help that you might have in getting rid of this strange behavior would be really appreciated. Thank you!
FINALLY.
Found the answer. Evidently there is a check box in the Layout Setup menu for "Show Field Frames when record is active."
Uncheck that.
Fixed.
The subgrids on my Form are set to Number of Rows: 250, and Automatically expand to use available space is checked.
This works fine for a short time, and the subgrids do dynamically size themselves.
However, ANY time new customizations are published, the subgrids go back to showing only 2 rows and some white space is added after the subgrid. Over time, the whitespace appears to increase. When I go back to the Form editor, the section containing the subgrid is all wonky looking (extra spaces under the subgrid). If I check the properties of the subgrid, they still show as indicated above.
As I understand it, this was to have been resolved with Rollup 17. The rollup download page indicates this as one of the bugs that were fixed: Removing / Adding any field to the form after enabling the option "Automatically expand to use available space" causes the sub grid to shrink or resize to much smaller in size.
However, the problem persists (and it's the most frustrating thing ever!)
Does anyone know how to resolve this? Alternatively, does anyone know how I can contact Microsoft to inform them of this issue without them charging me for a solution?
If memory serves this happens when more than one SUBGRID , IFRAME or TEXTAREA are set to automatically expand although only a single auto expand element is allowed / supported.
You need to reset all element with auto expand Save , Publish and then set the SUBGRID with auto expand again.
Dynamics CRM - Thinking outside the BOX
HTH
I am using LWUIT for series 40 for making my J2ME app and I have noticed a strange behavior of the LWUIT-Dialog while using the showPacked() method, the dialog being positioned with BorderLayout.CENTER.
This happens especially in touch phones.
I have attached an image in order to describe my situation.
Initially the dialog appears as shown in the first part of the image.However,it expands in the next few seconds to become like the one shown in the second part of the image.
Future calls to display the dialog using showPacked appears like the third one.I am clueless as to why this is happening.I want my dialog to appear like the one shown in the first half of the image all the time.Where have I gone wrong?
Note : The content of the Dialog is a an animated label.
I have no idea what the guys did there but I'm guessing they reflow the UI too aggressively. Try setting Dialog.setAutoAdjustDialogSize(false) and see if it solves your problem.
You can remove the title and background et al. with the code below, it makes only your animated GIF show with the dimmed dialog background :
setTitle(" ");
setUIID("Null");
setDialogUIID("Null");
getStyle().setBgTransparency(0);
getSelectedStyle().setBgTransparency(0);
getUnselectedStyle().setBgTransparency(0);
getPressedStyle().setBgTransparency(0);
getDialogStyle().setBgTransparency(0);
I am writing a MonoTouch iOS app. I have read many postings about ResignFirstResponder and I am using that.
My app is a typical table view app. I have done my own custom table cell view. The UITextField controls that cause the numeric keypad to come up in the first place are all on the custom table cell.
Currently I have it so that if you tap on the background of the cell I call ResignFirstResponder on all the text fields. This seems to work, but is not intuitive. I had a new beta tester get it last night and he tapped on one of the text fields and the keypad came up and he was lost as to how to get rid of it. After I told him to just tap the background, he now is fine, but obviously I want a solution that is obvious and doesn't require me to tell everyone how it works.
I read one post about a way to add a DONE button to the keypad, but it looked like a total hack and even broke when 3.2.1 came out and I don't want to have to worry about my app breaking when a new OS comes out.
Suggestions?
I would keep the background click->ResignFirstResponder that you have already, but add to it.
Curious, what button do you have set in the bottom right of the keyboard? There are options to show a Done, Search, Go, Next etc. buttons that can be setup to ResignFirstResponder. Pick the button that makes sense in your situation.
You can hook into the bottom right button by setting a callback to UITextField.ShouldReturn and calling ResignFirstResponder. You can just return false (that return value is for allowing line breaks in your UITextField).
Found an example here of hooking up ShouldReturn.
How can I scroll past the last link in a HTMLComponent? I am using LWUIT 1.5.
Moreover if the link spans over multiple lines, it stops on the first line, so the whole link is not visible.
HTML file for testing: http://bit.ly/uJ8RbN
UPDATE: The issue is here http://java.net/jira/browse/LWUIT-487.
Any workaround tips before the issue gets resolved?
Scrolling past the last link works properly in our test cases although its always possible there is a bug in the HTMLComponent implementation. If you found such a case please file an issue in the lwuit issue tracker in the LWUIT website and include the HTML that triggered the problem. The same probably applies to the long links issue.
A simple solution is to add an empty button to the end of the form, format the button to look like the background, without borders etc. This way after the HtmlComponent there is still a button that doesnt have focus but allows you scroll to the bottom.