Right now, if you have a screen with a button called BtnA that has a .Fill attribute of "Orange", for example, you can, on another screen, create a button called BtnB that will have a .Fill attribute of "BtnA.Fill".
My suggestion is to allow using the ".OnSelect" attribute the same way.
The reason for this is that I am currently using labels as functions (as seen in the screenshot below). I put all my operations in their ".OnSelect" attribute and they can call each other by doing Select(Lbl_SomeFunction), or a button can have an operation to select one of the labels. It is a great way to have some sort of "user defined functions", but my issue is when these blocks of code are repeated across multiple screens. If I need to modify one line in one of these labels, I need to go into all the other screens and edit that label's ".OnSelect" attribute.
If I could only have my operations written in unique labels on a screen, and then simply point to that screen's labels the same way you can point to another screen's component's fill color, as seen in my initial example, I wouldn't have to repeat my modifications on every single screen.
- LucasP1 on: Make Power Apps low code extensions be more access...
- mirm1 on: Send us your ideas for Inspection app in Teams
- Rens_ on: Send us your ideas for Employee Ideas app in Teams
- ScottDurow on: PCF - Web API Execute method
-
LVD
on:
Default message when a gallery has no items
-
PaulD1
on:
Licensing - Project Oakdale
-
LVD
on:
Support the This item for all Controls
-
rappen
on:
Binding FetchXML to Subgrid with reference to Reco...
-
JoeF-MSFT
on:
AI Builder Form Processing model training with doc...
-
ragavanrajan
on:
Multi User Development of Complex PowerApps