The tab buttons are in my main.lua and the when click action is simply composer.goto(“home”) etc
Thanks,
Matt.
Hi Matt,
Can I ask you to test something? When you switch to a new scene, add a scene transition effect like this…
[lua]
composer.gotoScene( “home”, { effect=“slideUp”, time=800 } )
[/lua]
…and tell me if the behavior is any different for the native fields.
Brent
This has worked to a certain degree, I have two sets of native fields at the top of the scene and one at the bottom (which is of the screen in the scrollview at the bottom). Rather than them staying on the screen when I change the scene it now removes the top two if on screen and moved the last up the screen if it wasn’t on screen. But if the bottom native field is on the screen and I change the scene then it worked perfectly. So this worked but still left one of the three native fields on screen if the scrollview was at the top of the screen.
Thanks,
Matt.
Hi Matt,
This is interesting. So basically, the behavior depends on whether the native field is on-screen or off-screen? They don’t move in unison with each other?
I made a quick example of how I think it is working at the moment.
a.1
On Forms Screen - When the page is first opened and the scrollview is at the top of the page, where the two native fields are at the top and on screen but the one at the bottom is off screen.
a.2
On Home Screen - Home button in tab has been pressed and all the native fields have moved up the screen. So the two native fields at the top are now off screen and the bottom one is now on screen.
b1.
On Forms Screen - When the page has been scrolled down to the so that the top two native fields are off screen and the bottom one is now on the screen.
b.2
On Home Screen - Home button in tab has been pressed and now the all the native fields have moved up after the scrollview has been scrolled so that no native fields are on screen any longer.
Hope this helps to fix this issue
Thanks,
Matt.
Hi Matt,
I probably need to look at your sample project at this point. Something is amiss, but it might be an obvious thing I’m just not detecting without seeing the code. Do you have a somewhat isolated project to zip up?
Brent
Yes that’s not an issue I have attached a copy into the attachments, bear in mind that the only way for the issue with the native fields is to build it and upload it to a device. As when I tried testing it in the simulator it looks as if there is no problems.
Thanks again,
Matt.
Hi Matt,
I experimented a bit with your project, and the results are a little odd. I had better luck, however, when I used left or right-direction scene transitions, versus up or down. When doing so, the fields didn’t seem to get “left behind” when moving around scenes. Could you test that out a bit and see if you get the same results?
Brent
Hi Brent,
It seems as if it has been the best method so far, it looks clean and simple which is great the native fields no longer stay on the screen as well. However, if you change between the scenes slightly too fast after changing scene it makes the opened scene go blank which is odd.
Thanks,
Matt.
Hi Matt,
This sounds potentially unrelated to the other stuff. Are you getting any error messages in the console/Terminal?
Brent
Hi Brent,
Oddly i don’t think there is, it only has a error with the fonts. I don’t know if that is the issue but i have no idea to be honest.
The error message looks like this
Windows simulator build date: Nov 18 2014 @ 18:35:32
Copyright © 2009-2014 C o r o n a L a b s I n c .
Version: 3.0.0
Build: 2014.2511
Platform: SM-G900S / x64 / 6.2 / Intel® HD Graphics 4000 / 4.0.0 - Build 10.18.10.3308 / 2014.2511
Warning: could not load font HelveticaNeue-Light. Using default font.
Warning: could not load font HelveticaNeue-Light. Using default font.
Warning: could not load font HelveticaNeue-Light. Using default font.
Hi Matt,
Yes, this is a font issue. Can you search all of your code for the term “Helvetica” and see if it comes up?
Brent
Hi Brent,
I did a search using Ctrl+F then typed in “Helvetica” and on every scene and page of my code it simply says
Unable to find Helvetica
Not sure what to do here,
Thanks,
Matt.
Hmmm… refresh my memory, which widgets are you using? Radio buttons if I recall? And what else? Buttons (widget.newButton()) or other widgets? Do you set the widget theme somewhere?
Brent
Yes I have radio buttons on my main.lua as the navigation and a few widget.newButton on my forms page just to navigate to some basic form pages with my native text fields and checkboxes.
Thanks,
Matt.
Hi Matt,
Please do a search for “setTheme” in your full project and see if you get any results…
Brent
Hi Brent,
I just tried a search through every file in my source project files and found nothing again I got the same result as the last search
“Unable to find setTheme”
Thanks again,
Brent.
Hi Matt,
Actually, this error you’re seeing is more of a warning, and it shouldn’t result in the app crashing or black-screening. That would be related to something else entirely…
Right I see, what do you think it could be, also I have discovered that my native fields scroll over my tab bar when I use my scrollView any ideas why this is?
My tab bar is on my main.lua
My native field are on my forms.lua
If that helps.
Thanks again,
Matt.
Hi Matt,
Native input fields will always appear in front of other visual (OpenGL) content. It’s a technical limitation and there is no workaround for it. If this is a breaking limitation, you could consider breaking up your submission forms into multiple pages which the user navigates (swipes) through, wherein the fields fit cleanly on that page and don’t interfere with the tab bar (thus no scroll view at all).
Brent