One thing to note in this update is that the assets when using companion are now saved at /sdcard/Makeroid/ dir, instead of /sdcard/AppInventor/ dir.
Your WebViewer’s GoToUrl function will work even when AppInventor dir is specified as it is replaced internally to use Makeroid dir.
This only breaks @Taifun’s PathToAssets block with Makeroid
well, that’s a bad idea to rename that directory
Makeroid is an App Inventor distribution, isn’t it? so why renaming the directory? it does not make sense imho…
Taifun
Well, yeah, first I thought that too
But also, an AppInventor folder could be confused into a junk folder or just a cache folder, due to it’s name (I’m not saying it’s a bad name, but maybe for new users of they see an AppInventor folder they can just delete it). With that we gain that if they see that Makeroid folder they know that that folder was created by us because they wanted too.
Also, new users of Makeroid, if they see AppInventor folder, they can think it’s a virus because they maybe won’t know that we are based on it
Plus, also, if users use either :thunkable: or or apart from :makeroid:, they can have separated assets paths
well, you like to attract other people, who currently use App Inventor or one of the other distributions…
for those people you made it now more difficult to change the distribution…
I will add into the documentation for the PathToAssets method, that this method is not compatible with Makeroid. Users will have to use the old manual method instead…
the assets when using companion are now saved at /sdcard/Makeroid/ dir, instead of /sdcard/AppInventor/ dir.
If you follow some threads here in the community, you probably now realize, that this decision was not a good idea… Especially after the rebranding to Kodular…
Let me suggest to change the assets folder back to /AppInventor to 1) not confuse people and 2) to keep logic as well as extensions in sync across MIT App Inventor and Kodular without having to use workarounds. .