@sim @jfperusse - not sure how I managed this. - I wouldn’t count it as a real bug just a bit confusing but after typing up a default template I found the buttons on the header greyed out. Pic attached.
Note: The buttons still operated OK and they look to have an underscore in them. Tried in V4 but didn’t see it there.
Note 2: it does happen in V4 and occurs when you start an edit. Is this a feature ? Haven’t noticed it before. Surely the buttons should be visible all the time ?
Hi @Bri_G. I’ve not been able to reproduce the issue where the buttons text isn’t using the right color, but we’ll keep an eye for it. Note that these buttons dynamically change their color based on what is behind them, as can be seen on this image when we have two tabs:
The underscore is normal.
@jfperusse @sim - I think I know what has been causing me a lot of crashes and freezing recently.
I usually set up Utils tab in which I place a function init() and within that I place the following line to name screen variables:
sW, sH, cW, cH = WIDTH, HEIGHT, WIDTH//2, HEIGHT//2
Just my laziness in typing. This has never been a problem for me until I set up a data tab to define button properties and used those variables in the calculations. I reported an issue with incomplete error alert which you have added to the list.
I now know what was causing the error - the variables used in the button definition were not defined which is odd as most of my previous projects have used that initialisation without an issue.
Then I realised it could be that since variable definitions are not done in global space but the table definition using them was in global space - that kicked up the error.
Placing the above screen variable definitions in global space (before function start()) resulted in the project running OK.
However - since the first crash I have been plagued with Codea crashing and freezing. It’s almost like my project damaged the Codea code itself or left a continuous running state saved with Codea so the error never gets resolved.
Have you made changes in the order that Codea components proceed in the latest beta ?
Edit: I think this issue is why the text in the menu buttons of the editor disappears. It’s almost like something in the editor display has been re-directed.
Switching off my iPad and restarting lets me run the other projects OK.
@jfperusse @sim - Latest update with this issue exported the trials I was using to investigate global table linked to button Class and deleted them from Codea, Improved a little after closing Codea and shutting off/re-starting my iPad and Codea. Managed to run many projects OK but still locked up on me. Have reported in crash reports.
Now installed latest issue but still seen the odd lockout of screen.
Also how can you tell if you have Codea Pro or the beta ?
The basic kicked me out on a couple of trials with over 500 lines of code. Note many of those were remmed out. If remmed lines are included in the 500 limit it could discourage new learning users from exploring further.
@jfperusse @sim - trying to resolve my issue with latest beta. Thought it may be an issue with iCloud as my allocation is getting full (so say Apple) so tidied that up.
Error still occurring and I’m getting an error report (see attached image) regarding a pipe. Could this be behind my problem .
Suggestion - whilst experiencing this problem, and trying to copy all of my projects to an external store, I became a little frustrated with the copy procedure. So, to cut a long story short would you consider adding a select option project files (a la Apple) so you can copy/move/delete multiple projects ?
It would cut down a lot of the faf that you encounter now and Apple must have routines for it that you can link into/use to do it.
@jfperusse @sim - Another feature of my problem - when the latest version of Codea starts - on the opening screen a button flashes up at the top but quickly disappears. I recorded the startup on my iPad, trapped the button and captured an image (attached).
It’s a button to get Pro, checked my version it’s 5.13 (417). I’ m just wondering if in my latest update something got corrupted.
@jfperusse @sim - just pulled in the side bar, from the right of the screen, and noted the Pro activation by purchase that has been referred to. Activated as suggested and changed the Codea icon.
After that I took a look at the Codea folder on my iPad using the Apple file manager and noted loads of projects and associated folders containing assets in the Codea root. Is that a result of upgrading to Pro ? If so can you explain what the objective is - I can’t remember downloading all those assets and there seems to be far more projects there than in the Codea project window.
What prompted me to look was trying to export all my current projects by using ‘export all’. It went on for ages before I cancelled it.
@sim @jfperusse - I seem to have resolved my problem. After moving all my Codea files from the current version I removed Codea from my iPad and re-installed again from the Apple Store. Now seems to be working fine. My apologies for the reams of post I have made. - it will be some time before I can re-instal all my recent projects. Thanks again for your help.
