@John @sim @jfperusse - noticed in the latest beta that style.fill() doesn’t have the selector at the end to enable colour selection, though fill() still works and does have the selector.
Also when selecting the colour in V4 it looked a much weaker colour with style.fill() than with fill() when using the same numeric values. May be due to the opacity value which you have to add manually when using style.fill().
Thanks for this feedback @Bri_G
Looks like there are some issues with color space in the default rendering mode in V4. I need to work on the style.fill() support as well!
Issue:
17.5.1 iOS
iPhone 12
Extreme unresponsiveness during task switching.
Switching to any other app and back causes Codea to be entirely unresponsive for up to 10 seconds or more.
Is my phone too old now? Is this an iCloud issue?
@sim - thanks for the upgrade, had a quick look around the system on my most recent iPad, installed on my older iPad and it has an oddity when listing projects (image attached). A series of projects are present with the default project icon, with project names that seem to be duplicate titles with a full stop at the beginning of each project name.
@Bri_G thank you for this report! Those should not be showing up… we’ll have to look into it
@sim - just to be clear it was not an issue on my latest iPad.
Further - when you open one of these ‘projects’ they open to a blank screen and a message saying ‘Failed to Load Project’. The icons at the top of the editing page remain greyed out.
The parameter.boolean call seems to be broken
@sim - I think I have found the reason why my iPad is showing up phantom images of projects (ie with the”.” present at the beginning of the project title. They are files that are present in my iCloud storage but not downloaded on that particular iPad. But I’m sure you know that. I think it is how you manage what project files are currently present on which iPad.
I think you need to add an iPad identifier to each file name rather than a “.” Use a letter or a number there say “A” for one iPad and “B” for another and something like # for not opened on any. So “AB” would be open on both iPads.
You probably have a better way of dealing with it.
You are right. Those files are supposed to show as non-downloaded Codea projects. We seem to have a bug! Will try to address in next beta
@sim - ooh, alternative idea, keep a file/folder for each iPad (on iCloud) that Codea logs into containing a list of filenames downloaded and filenames not downloaded. Can you use the iPad ID for the folder name?
Edit: possibly better yet - just a folder containing a list of projects downloaded for the relevant iPad.
Is this resolved for you? It was a bug that we fixed in an earlier beta
@sim - sorry not resolved but I have not received an update for Codea so I presume this is an iOS issue as my older iPad is on version 16.7.9 and my latest iPad is on 17.6. Can’t update the iOS to same version on my old pad.
Just noticed that on my old pad using the file app it shows up the files named with preceding “.” as the download cloud with down arrow icon present so I’m assuming that it’s due to a change in iOS.
It’s a bit annoying but I haven’t seen any other negative issues from it. I use the old iPad to check consistency in scale graphically to ensure users see the same image scaled to their screen.
Edit: on the second point the fileapp recognises that the file it is viewing in the iCloud directory is available for download ie not downloaded for that iPad. So iOS must have a flag related to that file. So if you can read that file download status, ie the flag, you must be able to avoid downloading it from within Codea. Would that get rid of the need to use the preceding “.” or is that the mechanism used by iOS ?
@sim @john @jfperusse- just noticed an couple of issues with dependencies in 482 -
I’ll check the latter as it could be just an iCloud issue.
Edit: yup, the section labelled documents is only showing up files which are local, but the files shown don’t fit the criteria for the search I entered.
Also, noticed that the iCloud icon, in the project icon list files, doesn’t show up very well against a light coloured background. It could be an idea to provide the icon with a stroke() using a good contrasting colour.
@sim @john @jfperusse - resolved the issue up to a point as I found a move to menu option in the filing options which enabled me to move a dependency onto my iPad. Could be better to include a copy to as well to avoid having to use the filing system options.
We’re trying to move away from the Dependencies as they are currently implemented. For now you can try depending on iCloud projects using the require() syntax at the top of your file:
Try adding:
require(asset.icloud.MyProjectName) at the top of your Main tab to import a project as a dependency
Thanks for reporting. Fixed in 3.12.1
@sim - thanks for the feedback, I was aware that *require * was available as I played with it when @jfperusse introduced it. I had thought that dependencies would be retained.
Thanks again
@sim - trying out your suggestion for using require and I ran into a problem getting the correct path - kept getting the error that file doesn’t exist. Could you describe the tricks with the syntax for requiring another Codea file.
Made me think - when you select a file and get the drop down info of that file (with iOS) a lot of information is provided from Get Info with iOS. That includes a where is, but it doesn’t seem that helpful. Is it possible to add a path for that file in the iOS drop down which is selectable so that you can copy the path and don’t have to worry about getting the path correct grammatically or syntactically in Codea, just paste in the copied path ?
Edit: another thought on this, when I’ve put the path into the require and tap on it the Codea dialogue pops up for file identification, in this case for “documents” showing inputs for folders or text. Do we need another option there for “projects” to use with require ?
Edit2: on investigating this further I note that in the text sections of the Codea import dialogue the entries are broken down into sources. iCloud and documents and I assume the order of display is taken from your Codea files order. I found the project I was interested in, in the documents section, and the separate project files were displayed and import options available. But I needed to use the file as a dependency or required. As is the function offered is great if you want to build up a project as stand-alone.
Is this the best place to add dependencies/requres. If so I suggest when you first display the dialogue you don’t display all the files just the sections, text/sprite/tabs etc together with the number of items in each section. Tapping on the section header to then display the relevant type assets. I would also default to alphabetical order as it would be easier to find the file you need that way - maybe with the option to choose project order versus alphabetical.
Edit3: - @sim - my apologies here, when I selected a text file of data, from another project, it actually loaded the data I needed. Could you clarify this - does the require only load the selected text files in another project or, does it use any of the text files from the required project ?
@sim @john - been running into issues with assets whilst trying to set up a common asset folder in iCloud for my project. To cut a long story short I have two Codea folders on iCloud both with the same name and with a different number of assets in each.
Whilst trying to set up a local list of sprites on a project on both iPads, using local sprites in the same asset folders, Codea froze on me and crashed.
Does each iPad generate a Codea file on iCloud with the same Codea name ?
If so does effectively using both folders raise confusion with Codea ?
On the setting up of a local asset list by ‘opening’ assets sprites into a local resource download the sprites into a local iCloud folder and just retain a text file address to that resource ? Or, is the asset downloaded into the Codea project file for local use ?
Second issue, on my old iPad, same project, had to build up the same assets list and change some of the asset addresses, fired up a number of red alerts to assets not found but still ran the project - don’t asset addressing path errors prevent the project running ? Or is this another clash/confusion with running iCloud assets with the same project on two pads ?
Crash reports posted on these issues.
Update: odd - can’t find the conditions where I had two Codea folders in iCloud. There are two Codea folders present but one has a small icon for Codea central in it the other hasn’t. Same view from both my pads now.
Did wonder if it could have been an iOS issue as new pad on17.6.1 but old one on 16.7.9.
@sim @john - point of clarification on the above post re duplicate folders.
When you type in asset.documents. does that default to the original file location ie those assets in the relevant folder on either the Codea local folder or the Codea iCloud folder or always on the local iPad folder ?
I hope that’s not too confusing, if the two asset folders are not in sync that may explain my problem.
I recently found an asset path as ‘(asset.documents[“images”])’ which was a little confusing.
