09-17-2019 17:24 PM - last edited 03-25-2020 09:17 AM
Thank you for this impressive tool - it really made my day!
I tried for a few hours without success to modify Themes.json to use a record variable instead of a single variable
(theme.PrimaryColor1Value instead of PrimaryColor1Value).
Your response to R3dKap from above made me realize that I need to start with a blank .msapp file exported from the Theme Editor app.
@R3dKap, thank you for having the same problem as me. 😉
Thanks for having a look - I'm doing a video on all of this soon to include with this post, as there was honestly so much to cover I couldn't do it all quickly enough in this article 🙀
Menu Example 1 & 2 both use MenuItems defined during the OnStart
Menu Example 3 uses MenuItems2 defined during the OnStart:
In terms of editing the actions/notifications that are triggered from menus, these are done using the button-trigger method - we store the code in buttons hidden to the normal user, and then have the code triggered from there instead of having to look through every object on the screen to find out where we have code running (I will be going into more detail on this in the video).
If you go to your Admin Settings screen and turn on 'Hidden Developer Things', you will see the buttons overlayed on the screen, which are part of the top-level group on each screen called 'Hidden Developer Logic Example 1/2/3':
Regarding your question about finding the MenuItems2Selected_Example_Dev the best way to search for any specific control such as MenuItem2Selected_Example3_Dev, is to type in the searchbar under Tree View which will search/filter your Screen/Control list 😺
In terms of editing the menus and collections - these are entirely contained within the App OnStart - the Set Theme button only applies the colours within the gallery, which are all defined during App OnStart.
In terms of Editing the actions that happen when you click items (whether notifications/patches/submits/ any code you can think of) - these I have defined using the buttons within the 'Hidden Developer Logic' group. You can create more of these and alter existing ones as needed.
I'd kindly ask that you please also wait for the long-form video which will be coming out within the next two weeks once I have some more time to work on it during the evenings, as there is certainly a lot contained in the Template that I would love everyone to understand but due to its size and complexity, there was only so much I could easily put into a written article without making it pages and pages... 😺
Thanks again for having a look!
Yes, the problem with creating your own template from scratch is that the structure of the App is different when Exported from the theme editor vs when Saved from the editor (this will also be within the video).
The Theme Editor creates a flat structure, with no folders, however, you can take the Themes file from a Saved Power App and insert it there too. I highly recommend this if you are planning on creating a template from scratch as this will definitely save a lot of time as the saved version from the editor will have all the latest properties and controls included (ie the stream control which is currently being rolled out to GA).
Thanks for the tip @Gabrz - that's really useful! I will give the PowerShell method a try myself later when I'm back home - I don't think most entry-level makers / citizen developers will be able to use PowerShell or even know of it, so I will be demoing the 7zip method within the video and have your method as a backup for those who have a bit more experience 😺
Finally figured it out.
Careful re-reading helps. 🙂
Indeed, the msapp file generated by the theme editor is much different and power apps reacts as expected when you open the msapp file in there.
Now checking what component properties are still missing.