I left the textinput control in edit mode and inserted a rectangle icon over the control and made sure to bring it to the front then I changed the rectangle fill collor to transparent RGBA(0.0.0.0)
I wanted the rounded corners and the label didn't offer that. This gave me a textbox with the border that could not be edited.
just put a rectangle icon behind id, or a label, set the fill color of the item in front to white for example and the item behind to another color, use formula on Y, X, Width and Height to create the BorderThickness.
yes, thanks, everyone knows you can add a rectangle or another control. to make another box for an outline.
As an app developer though, I don't want to be adding 100 extra controls to my display screens every week.
A workaround isn't a fix, and what I'd like to see is a fix from Microsoft, not a workaround that doubles my time to build an app screen.
Thanks again though for the comment.
@dave-jorgensen My workaround is to leave the controls in edit mode and place a rectangel with (color transparent) over those controls so they cannot be edited. Still a workaround but it dosn't take as long to line up and you can cover multiple controls at once if needed.
My first wordy response was lost because of an error so I figured I would try a simpler response first...
The rectangel around the field is not an acceptable workaround. Try creating, resizing rectangels 20 - 30 times and not making the form look wierd, especially if you have a view/edit toggle on the form.
Best soluttion in I see in the thread my opinion is set Form Mode.Edit and field DisplayMode.Diasbled. Then change the Disabled border, background, and text colors. In my case with an edit/view toggle, add an If statement for each of those. The transition looks smooth but its a bunch of work. Also, the control is still visible but you can keep that greyed out in the Disabled setting to indicate as much to the user.
As a potential solution that could save a huge amount of time for us citizen developers (who this was created for I think), could the View mode still show the border but remove the control, hint text, and maybe the tool tip to display the information to the consumer as intended, facilitate seamless transition from view to edit modes, and greatly reduce development time for those of us whose main job is not this... lol.
nope, there is no solution. Setting DisplayMode to view removes the border. that's the issue, workarounds don't address the actual issue.
Ideally it would be nice to have properties for the border when in view mode just like the properties where you can set the DisabledBorder color/thickness.
but Microsoft doesn't seem to have any interest in doing so. As they stated earlier, the existing behavior is by design. But that's completely the wrong approach. It's by Microsoft's design, and here the users of the product are saying they'd like the design changed. It's just adding a couple more properties to the control, would probably take 10 minutes for the team to actually do the work.
Check out the on demand sessions that are available now!
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
Features releasing from October 2020 through March 2021
Una semana de contenido con +100 sesiones educativas, consultorios, +10 workshops Premium, Hackaton, EXPO, Networking Hall y mucho más!