@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 ?
