Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Codea 3.2 (215)

SimeonSimeon Admin Mod
edited April 23 in Beta Posts: 5,364

This latest beta adds support for pointers (mouse and trackpads)

  • Code editor interactions re-written
  • Pointer effects everywhere
  • iOS 13 only
  • New hover(x,y) function and POINTER touch type
«1

Comments

  • dave1707dave1707 Mod
    Posts: 8,398

    @Simeon Downloaded the latest version. I guess there’s nothing I can test. I’m strictly a couch coder and I only use the built in keyboard. I bought an external keyboard for $3 just to try it and I totally hate it. It’s been a long time since I’ve sat at a desk and written anything.

  • SimeonSimeon Admin Mod
    Posts: 5,364

    @dave1707 the actual touch-based code editing is completely rewritten too!

    For example, no more magnifying loupe (dragging the cursor behaves like any standard iOS 13 app). Same with the selection loupe. Scrolling and dragging behaviour also changed (hopefully for the better). If you notice anything buggy about it please let me know, otherwise I'm keen to release it to the store

  • dave1707dave1707 Mod
    Posts: 8,398

    @Simeon I think I mentioned this before, but for some reason the screen started scrolling towards the bottom of the code by itself. It was scrolling about 10 lines per second. I could scroll to the beginning of the code and after about a second it started scrolling towards the bottom. I don’t know what caused it and it stopped after I started messing with the screen.

  • SimeonSimeon Admin Mod
    Posts: 5,364

    @dave1707 This just happened in build 213? Thank you for the report this is exactly the kind of bugs I'm looking to fix

  • dave1707dave1707 Mod
    Posts: 8,398

    @Simeon The scrolling problem happened in the previous release. I’m trying to find where I first mentioned it, but I haven’t found it yet.

  • SimeonSimeon Admin Mod
    Posts: 5,364

    @dave1707 ah okay that's good, because this release has the edge-scrolling behaviour entirely re-written. Hopefully that bug got squashed with this release

  • dave1707dave1707 Mod
    Posts: 8,398

    @Simeon I guess I didn’t understand your question completely. The scrolling problem first happened in the previous release 3.1 (208) and then just happened again in this release 3.2 (213) .

  • SimeonSimeon Admin Mod
    Posts: 5,364

    Oh I see, that's interesting that it happened again. I'll try reproduce. Thanks for the clarification

  • edited April 22 Posts: 1,726

    @Simeon I am finding the self scrolling of this new version a nightmare. Especially when I am selecting a section for copying. It’s worse in landscape mode. It must be down to sensitivity of the touch near the bottom of the editing window. The narrower editing window area in landscape means selection can easily control scrolling.

    In general the feel of the editing window is faster and slicker than the previous version but the selection procedure needs attention. Would it be possible to introduce a select at start(double tap) and a select at end(another double tap - or other combination) as select and drag is frustrating.

    Edit: another feature with this version is that, when pulling out an error bar from the right it can result in scrolling of the window.

    Another thought on the selection system double tap to start followed by long press for end.

  • Posts: 534

    @Simeon, like @Bri_G i find it more awkward have to tap, then choose select, then drag to make a selection, Perhaps a long tap could go directly to the start of the selection?

  • SimeonSimeon Admin Mod
    Posts: 5,364

    @Bri_G excellent feedback, thank you. I'll can tone-down the edge scrolling behaviour and fix the error bar behaviour

    Tap to start and end is interesting, though I'm not sure I can think of a great way to do it for this version. You can drag in the line gutter to select multiple lines too

  • edited April 22 Posts: 1,726

    @Simeon - noticed another issue, on a couple of occasions I have had trouble placing the cursor at the end of a bracketed list. Trying to tap it in place moved the cursor to the front of the next line, trying to place the cursor after the final bracket and cursor move left moved the cursor to the end of the following lin. Even with a cursor just before the final bracket didn’t allow insertion of the cursor. I could place the cursor after the bracket and move it left to the end of the variable list but tapping on it to begin editing moved the cursor to the beginning of the next line.

    Oh, by the way did you see the suggestion for double-tap and long press for area selection?

  • SimeonSimeon Admin Mod
    Posts: 5,364

    @piinthesky a long press should directly start a selection, it does for me. Long press on a word, the selection bubble will pop in, then drag up or down to continue it. You can also double tap to immediately select a word, triple tap to select a line (or single tap in the line gutter)

  • Posts: 534

    @Simeon, yes indeed that seems to be the case-good.

  • Posts: 1,726

    @Simeon - selection of text working well in 214 now, now a smooth editor. Am occasionally seeing the scrolling that @dave1707 mentioned earlier and am still seeing the placing the cursor at the end of brackets problem - but you can add further parameters by placing a comma and typing directly it appears it is the second tap that moves the cursor.

  • edited April 22 Posts: 1,726

    @Simeon - a little more info - I was used to being able to place the cursor at the end of a bracketed parameter list. You can do that by you need to be targeting the last parameter not the space between the last figure and the end bracket. I can get used to that. Tapping the cursor at the end of the parameters is usually needed when pasting additional data, by tapping the last parameter the cursor is now placed at the end and a second tap on the parameter allows pasting new data at the end. So it is workable but I think subtlety different to previous editing.

  • edited April 22 Posts: 1,726

    @Simeon - another point I noted which looks different. When I selected a parameter value in a vec3() the whole contents of the vec3() were selected ie all the x,y,z parameters. Is that as expected.

    You seem to have taken all the ‘padding’ out of the code lines- so at the front and back of the line the cursor is placed where you’d expect - neat.

  • edited April 22 Posts: 1,726

    @Simeon - while editing code after a multiple condition if then the then was displaced so I started deleting the padding in front of it when I did some code disappeared and an error (normally in the parameter window) was pasted into the code. See attached image.

    Edit: in addition to the error insertion I just found out it also deleted a tab with data in.

  • dave1707dave1707 Mod
    Posts: 8,398

    @Simeon I started a new project and I felt like I was fighting the editor most of the time. I couldn’t place the cursor where I wanted it. It seemed like the cursor was going either to the right or left. I had to keep tapping the screen to place the cursor close and then drag the cursor where I wanted it. I usually copy chunks of code, paste it someplace, and then modify the copied code. Trying to place the cursor exactly where I want it in the existing code is my problem.

  • edited April 22 Posts: 1,726
    @Simeon - what are the requirements for linking mouse to iPad, tried linking one of my logitech mice but no joy - want to test with Codea.
  • dave1707dave1707 Mod
    Posts: 8,398

    @Simeon The undo key doesn’t work.

  • Posts: 1,726
    @dave1707 - thanks for logging that, I found it when I had the error posted in code, but I thought it was an after affect from that.
  • Posts: 534

    @Simeon i used to comment out a line by putting the '--' in the first two columns, now they are indented next to the code, so it is different. I guess i can get used to it, but strange not to able to put them where i want.

    Also, if i use the long press to initiate a text selection, it really takes a long time for the blue markers to appear at the start and end of the grey selected area.

  • dave1707dave1707 Mod
    Posts: 8,398

    @piinthesky I can put the —— anywhere I want. They can be left justified with as many spaces between them and the text or as many spaces before the —— and the text.

  • dave1707dave1707 Mod
    Posts: 8,398

    @Simeon I don’t know about anyone else, but I find the new editor really frustrating, to put it mildly. I don’t know if it was changed to make the support for the mouse or trackpad easier, but using the builtin keyboard is a pain. I’m spending more time trying to get the cursor where I want then doing actual coding. It’s like I’m constantly tapping on the screen to get the cursor near where I want to type, then finding the cursor and dragging it exactly where I want to type. A lot of times I end up selecting ranges of code, then I have to tap to unselect it, then try to move the cursor again. It’s like doubling or tripling the time it takes to do something. I’m not finding this enjoyable.

  • SimeonSimeon Admin Mod
    Posts: 5,364

    @dave1707 thanks for the undo key bug report. Fixed for next build

    Yeah the cursor placement is different because it now follows the standard iOS editing conventions (like other apps, e.g., Notes). I'll look into how much control I have over it

  • SimeonSimeon Admin Mod
    Posts: 5,364

    @dave1707 I'll see if I can make it place the cursor exactly where you tap like it used to.

    The change was more to eliminate many thousands of lines of my own code which tried to recreate Apple's text editing experience (rendering selection handles, the gestures involved in moving them, how the caret blinks and moves) and replace it with the standard system behaviour now available in iOS 13. I felt like this would make the code base easier to maintain, and it also had the advantage that I didn't need to try to emulate Apple's trackpad and mouse support in text editing

  • dave1707dave1707 Mod
    Posts: 8,398

    @Simeon I thought it was something like that. It seems Apple never does anything to make things easy for the user. Then usually when they fix something they break something else. What they’re doing might work for things like Notes and the likes, but for editing code that has numbers, commas, brackets, math symboles, etc, it’s not working very well.

  • SimeonSimeon Admin Mod
    Posts: 5,364

    Just to get clear on your feedback, your main issue with the changed behaviour is:

    • Caret doesn't land exactly where you tap, instead it goes to the start or end of a word and you have to drag

    If I can fix that one, would that make the new editor OK for you to use?

  • dave1707dave1707 Mod
    Posts: 8,398

    @Simeon The cursor placement was the biggest problem. If the cursor went where the touch was, like the old way, then that would work. I don’t think anything else was a problem.

  • SimeonSimeon Admin Mod
    Posts: 5,364

    @Bri_G do you also prefer the old cursor placement behaviour? That it goes exactly where you touched rather than to the start/end of word

  • Posts: 1,726
    @Simeon - in one word yes. If the Apple system just needs tuning to the Codea editor then I would probably adapt but at the moment, in this beta, as @dave1707 said - it takes a lot of pleasure out of coding.

    I''ve always liked the built in editor but discovering MS code and easy pasting in code from my Mac has given me a useful option - not checked that option with 214.
  • SimeonSimeon Admin Mod
    Posts: 5,364

    @Bri_G thanks for the response. So you would prefer the text insertion point lands exactly where you tap? Good to hear that you agree with dave

  • Posts: 505

    I'd prefer it this way as well

  • Posts: 534

    and me

  • SimeonSimeon Admin Mod
    Posts: 5,364

    Codea 3.2 (215)

    • Caret now lands precisely where you tap
    • Undo menu item and keyboard button work again
    • Fixed bug where output pane aggregation bubble could appear on the left
    • Fixed appearance of find/replace editor highlight in dark theme
    • Xcode export updated to remove AudioKit dependency
    • When using a trackpad, hovering over the tab bar in the code editor will make it slide down if not visible
  • dave1707dave1707 Mod
    Posts: 8,398

    @Simeon Just a quick response, the placement of the Caret is perfect, thanks. Will test the other changes as I have more time.

  • Posts: 1,726

    @Simeon - just loaded 215 - thank you!. Can now place the cursor where you need it, you can even select and edit one parameter in a vector like vec2(x,y,z). I'm afraid your going to have to resign yourself to the fact that you have created a better editor than the fruit.

  • SimeonSimeon Admin Mod
    Posts: 5,364

    Thanks for the quick feedback @dave1707 @Bri_G, glad that fixed it for you!

  • Posts: 534

    @Simeon, nice-that work fine for me.

  • dave1707dave1707 Mod
    edited April 23 Posts: 8,398

    @Simeon Ran into a minor problem. If I tap on the screen to get the pop up to select, select all, paste and choose select all, I can’t get a prompt that says copy.

    PS. If you tap on a line number to highlight (select) the line, you don’t get the copy pop up. If you grab one of the drag icons and drag it to select 2 lines then back to one line, you can get the copy pop up.

  • Posts: 1,726
    @Simeon - loaded 215 this am, but just before loading was having a little trouble with 214. In landscape programming with keyboard up. Selected section to copy - so highlighted in blue. Tapped to lower keyboard and format on selection disappeared. Tapped to remove selection and keyboard rose and selection re-appeared. Can't remember seeing that before. Will check out 215 when battery recharged.

    May not be an issue after you updated to 215.
  • dave1707dave1707 Mod
    Posts: 8,398

    @Bri_G It appears the code can only be selected if the keyboard is showing. If you have code selected and hide the keyboard, the selected code is unselected.

  • Posts: 1,726

    @dave1707 - thanks for confirming that, don’t know if that has always been present. My problem was a large selection highlighted off-screen in landscape mode. Didn’t think to rotate, just dropped keyboard. Not an issue, just need to think before I do anything. Consequence of giving these sophisticated toys to an idiot - ie me!!!!

  • SimeonSimeon Admin Mod
    Posts: 5,364

    @dave1707 that missing "Copy" menu bugs me too. I'm not sure why it doesn't show (I no longer have control of the menu's appearance)

    At the moment you can drag the selection handle at the start or end and let it go in the same place to make the menu appear. I'll look at whether I can force the menu to show on Select All

  • Posts: 1,726

    @Simeon - could you add the select all as a menu option from the top menu?

    Alternatively you could add it as an option on a tab, in that way it could be easy to copy a tab from one project to another.

  • SimeonSimeon Admin Mod
    Posts: 5,364

    Oh as an option to long pressing tab is a great idea! Thanks for the suggestion

  • Posts: 6

    Talking about tabs it would be great if you could add the following in one of the next releases (just a suggestion):
    1. Single tap on an active tab opens a list off all functions that are defined in the tab for quick access, i.e. tapping in the list scrolls the page down to the function definition and sets the cursor there.
    2. Double tapping the tab scrolls to the top of the page.

  • dave1707dave1707 Mod
    Posts: 8,398

    @Simeon I hope you can do something about the copy, paste, select and whatever else. They’re almost as bad as what the cursor problem was. It takes multiple tries just to do something that was easy before.

  • SimeonSimeon Admin Mod
    Posts: 5,364

    @dave1707 it's fixed in the next version (3.2.1), just waiting for Apple to approve the beta while also waiting for them to approve 3.2 for the App Store

    @TheMojoMan jumping to a function quickly is on my to-do list. Love the scroll-to-top idea

Sign In or Register to comment.