Teie kommentaarid
This bug is specifically related to the option of adding a page before the first page.
Before this is fixed, it should work if you click "Select All" and then "Copy" so that you have everything from that new page and then delete the page.
Next, add a new page that's somewhere else in the app, not before the first page, and paste the elements. Then in the page manager you can change the order of the pages to make this page before the original first page.
Let me know if you have questions about any part of the process.
Before this is fixed, it should work if you click "Select All" and then "Copy" so that you have everything from that new page and then delete the page.
Next, add a new page that's somewhere else in the app, not before the first page, and paste the elements. Then in the page manager you can change the order of the pages to make this page before the original first page.
Let me know if you have questions about any part of the process.
Hi, it looks like I misunderstood you, I apologize. I thought you wanted the user to be able to click while the hint is visible, but it seems that in the current build the area where the hint had been can no longer be clicked, even when the hint has faded out. I'll describe this bug to the developers. Thank you for pointing this out!
In this situation, I would note the action sets that the drawer has and add them to the hint element. For example, if the drawer has Tap-Animate (Self), then to the hint I would add Tap-Animate Drawer, and maybe Tap-FadeOut (Self) as well so that the hint disappears once the user has found it.
In some cases, elements that start out invisible but appear later are still necessary for interactions, so I think it would be best to not exclude them from picking up interactions.
In some cases, elements that start out invisible but appear later are still necessary for interactions, so I think it would be best to not exclude them from picking up interactions.
Hi Truman,
The matching behaviors work a little differently in IB4, so I'm working on updating the instructions in the user guide. I'll post them here as soon as I finish. Basically, instead of the "Matched" and "NotMatched" interactions, we have conditions: "If Match of {MatchText} Occurred" and "If Match of {MatchText} Did Not Occur."
The matching behaviors work a little differently in IB4, so I'm working on updating the instructions in the user guide. I'll post them here as soon as I finish. Basically, instead of the "Matched" and "NotMatched" interactions, we have conditions: "If Match of {MatchText} Occurred" and "If Match of {MatchText} Did Not Occur."
Hi Jen,
If there is only one area per page on which the user can type, you might consider using a note element instead of a text element with SetText, because with notes the user types directly into the space instead of typing in the pop-up window. You can click here to read more about note elements: Notes.
If there is only one area per page on which the user can type, you might consider using a note element instead of a text element with SetText, because with notes the user types directly into the space instead of typing in the pop-up window. You can click here to read more about note elements: Notes.
Thank you so much for the demo. I've reported this to our lead developer with a link to the video.
Customer support service by UserEcho
To make it so that a certain word within a text element can link, you can add a new graphic element and, without assigning an image to it, place it in front of the word that should link. Then you can add the Tap-Browse action set to this transparent graphic element.