Twoje komentarze
Just to give you an update, this bug is still in the queue. I will let you know when it is complete.
12 lat temu
Tyler,
Let me look into this a little more and get back to you.
Let me look into this a little more and get back to you.
Matt,
The best way to acheive this is to create a transparent panel onclick and use the onhover action to drive any dynamic movements. Similar to the example above. This isn't really something we have spent a lot of time on, but if you have well defined requirements, I could look into it deeper. There might be something we can do to make it work.
The best way to acheive this is to create a transparent panel onclick and use the onhover action to drive any dynamic movements. Similar to the example above. This isn't really something we have spent a lot of time on, but if you have well defined requirements, I could look into it deeper. There might be something we can do to make it work.
This is currently how it is supposed to work. We do have a feature enhancement ticket logged to allow placeholder text in a multiline text field.
Thanks for the follow-up.
Our Android Engine is now in a beta phase and it's being used to build a handful of Apps for specific target clients. As we vet the engine and capture data we continue to work on making the necessary steps to make sure that our App Creation Studio has the changes needed to accommodate both Android and iOS.
In the short term we are planning on releasing the Android beta version of fusebox in the Google Play store very soon (read: this month), so while publishing capabilities will still be unavailable for Studio users, you will be able to test and create in the Android environment using WIRE.
Our Android Engine is now in a beta phase and it's being used to build a handful of Apps for specific target clients. As we vet the engine and capture data we continue to work on making the necessary steps to make sure that our App Creation Studio has the changes needed to accommodate both Android and iOS.
In the short term we are planning on releasing the Android beta version of fusebox in the Google Play store very soon (read: this month), so while publishing capabilities will still be unavailable for Studio users, you will be able to test and create in the Android environment using WIRE.
Have you tried using a set action?
https://studio.rarewire.com/wordpress...
This will let you change your onclickup based on an action trigger. This can be added to the action that changes the panels to ensure that the onclickup changes to the correct action.
https://studio.rarewire.com/wordpress...
This will let you change your onclickup based on an action trigger. This can be added to the action that changes the panels to ensure that the onclickup changes to the correct action.
Doug,
I tested this scenario using the code you provided above and it looks like there is a bug with fit="yes". I will see what I can do about getting this corrected, as it works on our Android engine.
In the meantime, can you use height="fit" to achieve your goals? I will follow up with you on Monday to let you know the status of this bug.
Thanks.
I tested this scenario using the code you provided above and it looks like there is a bug with fit="yes". I will see what I can do about getting this corrected, as it works on our Android engine.
In the meantime, can you use height="fit" to achieve your goals? I will follow up with you on Monday to let you know the status of this bug.
Thanks.
This is probably the result of the text tag not knowing what the actual height of the text tag is (since you are using height="fit") so it can't resize if it doesn't know that attribute. Change your height to something static and see if that allows the fit="yes" to trigger.
Try taking fit="yes" off of the text tag and only use the one on the style, it might be clashing since you have it twice.
what does your style look like?
Customer support service by UserEcho
