@Jmv38 the newest build 2.1 (6) should fix your issues with displayMode() and supportedOrientations()
@JakAttak @Jmv38 do you know how it came about? (Getting stuck.) Has it happened often?
@Jmv38 could you provide the 3000 line code that you tried to paste? Maybe on pastebin or something, so I can try it out.
@JakAttak I understand why you aren’t able to exit during a printed infinite loop, but I’m not sure how to fix it yet.
@Simeon.
1/ the width and height problems seem solved. Thanks!
2/ here is the long code: http://jmv38.comze.com/CODEA_4/buttonLibrary.txt
Opening Shader lab always crash 2.1 (6) for me. Same issue when opening from projects drawer or shader picker. It stay 2/3 sec open and exit.
When opening from the edit button of the shder picker, the left panel is opened and nothing and the shader I’ve picked for editing is not here.
I don’t know if it’s project specific, testesd from an empty one and the shader sample.
Small thing, the text editor does not reflect the text size defined in user preferences. And I’ve never noticed before and that don’t really matter but in the code editor, the text antialiasing look blurry with a size 16 > s > 20 than 14 15 16 or 20.
Thank you @toffer. I must have introduced that issue when fixing the displayMode one. I’ll look into the text size issue.
@Simeon, not sure how to reproduce it, I’ve tried a bit, but it seems to be random.
Here’s something stopping me from running my game… Happened after I rewrote the readImage function and stays there even if I comment out that line, it appears as the normal error banner for a split second then goes, still unable to start the project with a red shade on the tab:
https://www.dropbox.com/s/0errst9falmmxp1/Photo%2018-08-2014%2000%2032%2035.png
Edit: Also happens even if I comment the whole page
@toffer when you say the text size does not reflect the text size in user preferences — do you mean the text size specified in the Settings app on your iPad? Or the text size specified in the Codea settings panel? The latter seems to work fine for me, and the text looks okay here, are you able to show a screenshot?
@Luatee so the beta install issues are all worked out now? The next build should stop the errors from disappearing, so you should be able to see what it is then and let me know.
@Jmv38 @JakAttak I’ve optimized the code editor for pasting and deleting large amounts of text. Hopefully this will solve your issue.
@Simeon they are, I lost a tiny bit of work but nothing of any worry. It seems a lot more responsive, I fixed the error and it was because of an error in a dependency that it occurred. I can reproduce it and send you a project if you’d like?
####Suggestion:
When the program is stopped, this often occurs during the draw(). Then there is an incomplete drawing on the last image. This is functionnally ok, but gives a ‘buggy’ look to the project. Could you consider waiting to have finished the draw loop, for 0.2s max, before actually stopping the program? The feeling would be better.
If I switch apps for a couple of seconds, and come back, Codea is frozen and restarts itself. This is incredibly annoying and definitely did not used to be the case (note I am on iOS 8 so it could be a combination of that and the new update)
@JakAttak are you sure that it’s doing that in the latest build — 2.1 (8) ?
I think that the default ellipseMode has changed to RADIUS instead of CENTER as it says in the documentation.
@Simeon, I was on #6, oops. Appears to be fixed in #8, thanks.
####Bug:
the button on top right of keyboard doesnt work any longer.
@Jmv38 the play button? Or do you mean += (I think there is a bug with += where it is disabled inappropriately).
@Andrew_Stacey thank you, will look into it.
Just going back to when parameters fire, why not include an optional true/false parameter as Jmv suggests, and default it to the old behaviour? Then it is backwards compatible but allows us to defer execution if we want to.
@Simeon, for me both - play button never works when showing keyboard, only works 40% of time when keyboard is down. += button is often grated out when i should be able to use it. (Side note: table.number then += results in table.number = number + as opposed to table.number = table.number +)
@JakAttak thanks, I’m aware of the second issue (+=), but I didn’t realise the play button wasn’t working. Is this something that has been happening recently, or has always happened?