We might want to have a special case on the top level form to block
opacity/transparency manipulation.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email
EDIT: just found the origin of the issue. In my Login Form I had "
setInlineAllStyles("transparency:0; opacity:255; alignment:center;");" .
Removing
the "transparency:0" parametter solved the issue.
On Monday, March 26, 2018 at 10:25:22 PM UTC+2, Steve Hannah wrote:
>
> It appears that
I put you a small example on
github: https://github.com/ramsestom/CN1GUI_test in case this can help you
track the issue (this is the login form layout that is broken on the
simulator or on a real android device).
On Monday, March 26, 2018 at 10:25:22 PM UTC+2, Steve Hannah wrote:
>
> It
It appears that initFirstTheme() sets the global resources file. This is
the effective difference, as when you call the no-args constructor of your
form, it uses the global resource file. I'll need to look into it deeper
to see what the correct behaviour should be (whether the result you're
I just copied the source code you posted directly into a project that uses
the blue theme, and this was the result in the Simulator.
I'm not sure why you'd be getting different results. Perhaps your project
is using an older version of the libs. Make sure that:
1. Your Codename One plugin is
The SignInForm UIID was the source of the issue. Thanks. (Not sure why
taking a screenshot changed the layout though...)
I now have another issue with the simulator.
Here is the source code of my class generated with the GUI builder:
import com.codename1.ui.Form;
public class Launch extends
All UIID's exist. You will get the default UIID value when you use
something that doesn't exist. Since the default value (which you can edit
in the designer) is transparent the form is transparent and you get
problematic behavior.
We could check for transparent forms but this might be a
The "SignInForm" UIID was the issue (would be nice to have an exception
thrown in the simulator console when an UUID doesn't exist). Thanks
I have another issue with the simulator.
Here is the code of my Form produced by the new GUI builder:
import com.codename1.ui.Form;
public class Launch
The "SignInForm" UIID doesn't appear to be picked up. Note: If you
comment out that line, it works fine.
setUIID("SignInForm");
So double check and make sure that you are working with the same theme file
- and that the SignInForm UIID is registered in that theme file.
Steve
On Thu, Mar 22,
