It looks like you're new here. If you want to get involved, click one of these buttons!
This version updates the autocomplete bar and has a lot of underlying code editor changes
What to test
- Please test autocomplete for code and assets
- Try long pressing various autocomplete suggestions
- Try wrapping long lines in the code editor
New Autocomplete bar
- New design. Autocomplete suggestions replace the top row of input buttons
- Colour coded suggestions
- Scrollable when there are lots of suggestions
- See an autocomplete suggestion with an underline? Long press it for instant documentation
- Try autocompleting your asset keys, you'll get neat icons showing their file types
- Long press on the autocomplete suggestions for assets for a visual preview
This update also includes a big code editor change:
- Line wrapping is completely changed. Wrapped lines now indent at the same level as the initial line
Accessibility changes
- Autocomplete suggestions follow editor font size
- Gutter line numbers track editor font size
Comments
@Simeon Playing with autocomplete. I keyed an a then selected asset. I then keyed the . and long pressed documents. Codea hung for approx 10 seconds.
@Simeon I’m running into various delays with autocomplete. If I key a for asset then tap asset, key the . then tap documents then tap the . there is a delay before the . is accepted.
@Simeon I think I found out why there’s a delay when I do something with documents. The autocomplete bar lists every one of my projects. I have over 600 projects so the autocomplete bar is really long.
@Simeon Here's something else I ran into. I just had a bunch of random letters to force line wrap. The function setup() was at the top of the screen and when I hit the run icon, it shifted down the screen. See image below.
PS.
The problem doesn’t have anything to do with long lines. If there’s a code error, that forces the problem. Key the below code and press run.
@Simeon - Codea crashed when I was cutting from existing code, in the same tab, and pasting into a statement. Video recorded will try to attach. Video too big will reduce and post later.
Also can reiterate slow response on asset listing and when trying to delete asset components - which resulted in half line disappearing as I didn’t know if the touch had been accepted hence multiple touches.
Also some issue with selecting screen - selected all of screen. Plus screen scrolls awkwardly when trying to select - especially in landscape.
Also - with remarked long lines the remark wraps but also drops a line below the — REM characters.
Here is youtube link address:
Sorry about the advertising - didn't know that would be added.
How can I access the beta?
@skar You have to be given beta rights by @Simeon .
@Simeon Here's another problem. The error message is skinny. See image.
@skar happy to include you if you're willing to provide feedback. DM me your email address for an invite
@dave1707 thank you for those examples, I'll profile the autocomplete bar with 600 file system items and try get performance better. The editor bugs look fixable too
@Bri_G that crash looks bad! Does it happen every time? Does copying and pasting in that exact text do the same crash? If so can you share the code here with instructions on how I can cause the crash on my iPad for debugging
@Simeon - happens every time, and tried pasting in different locations but still crashes. I was trying to tidy an initial project up and expand it to add further features so the code is a bit of a mess. Intended posting later in the forum so here is code:
Will also include the relevant csv and image, if the image isn’t too big.
Note: whilst copying code scrolling down from top to bottom to select - as soon as you reach the bottom the copy menu appears then disappears. Difficult to get menu up by selecting the selection handle at the bottom - it tends to move up a couple of lines. So I copied what I could but had to add the end } bracket in this forum post. Tied up with editor problem with cursor at bottom - no free space/lines mentioned earlier.
@Simeon - resolved the problem - it was a clash between two arrays. Modified code added below. Note deleted touch as not used at moment and added small extra routine. Did this in previous version which did not crash. Believe this may be due to two errors incurred at once.
If, ignoring my bad programming, hope you can see the changes and dig out the cause of the crash and, of course, resolve it.
@Bri_G I tried pasting
planets[starter]
intonum[gl] = <pasted here>
but was not able to produce the crash. Did I do it wrong?@Simeon Here’s what @Bri_G might be saying. Load the below code. Double tap on asdfghjkl to select it then select Copy. Move the cursor to the end of the line. Press return to create a new blank line. Tap on that new line and do a Paste. Crashes every time.
@Simeon Here’s another problem. Double tap on asdfghjkl to select it then select Copy. Try to paste a copy after zxcvbnm.
@Simeon Under certain circumstances, I’m having a very difficult time trying to place the cursor where I want it. I’ll just give up and let the cursor go wherever it wants and then I’ll drag it to where I want it.
@Bri_G Now that I see what your CSV file looks like, here’s another way to read it and populate the fields in a table. The table planets is now a multiple array table with the different planet values per entry.
@dave1707 - spot on with you bug finding. Noted that dropping the bracket off of the end of a function call to paste a string into it crashed Codea, but getting the menu up with the cursor within the brackets is a nightmare. Frustrating. Cursor location does seem very difficult it tends to offset from the touch. It is also reluctant to go into a () bracket pair.
@dave1707 - on your suggestion for reading of the csv - thank you. That is more or less what I was trying to introduce butin my casr, in a very untidy way - by both cleaning up and adding new features. Messy. I'll implement that with relevant conversions where necessary on building the properties involved. Thanks again.
why autocomplete from other projects, unless dependent?