PR opened for those docs! Thanks for your hard work. You might want to open a thread to openly work on your studies material. I don’t know what direction those need to go to fit in with the existing one.
Also, super work @scanner_darkly! Love the ternary op and the implementation of multi-line select.
when editing scripts you can now use Shift-<up>/<down> to select multiple lines. when more than one line is selected the edit line (the bottom line) does not display anything, and to return to editing you can either press <Enter> or select a single line. pressing <up>/<down> will also make it go back to single line selection.
other fun things you can do with selected lines now:
Alt-<up>/<down> will shift selection up or down
Alt-<delete> will delete selection without copying it into the buffer
toggling comments with Alt-/ will work with multiple lines as well
all the old shortcuts for cut/copy/paste will now work with multi line selection, and you can still use them with single lines as well. however, there was a change in behaviour i had to make: when pasting, it will paste at the current position while shifting what was there down. previously, when you pasted something, it would paste into the edit line, so to commit the paste you had to additionally press <Enter> and it would replace the currently selected line with whatever you pasted. now it will shift the currently selected line down and it will insert the pasted line(s) above.
this seems like the most intuitive approach but i’ll be curious to hear how people find it in practice. you can somewhat replicate the old behaviour by copying, then selecting the line you want to replace, pressing Alt-<delete> and then pasting. i’m also considering adding this: when pasting a single line, and the edit line is empty, replicate the old behaviour (paste into the edit line but don’t commit). this way you can also replicate the old behaviour by copying a single line, then navigating to the line you want to replace, pressing Shift-<backspace> and pasting.
the buffer is shared between script editing / live screen / preset writing screen. i still need to add support for multi line selection to preset writing screen, once it’s done one thing you could do is use it to store bits of scripts!
finally, you can now navigate by words using Ctrl-<left>/<right>. i’m hoping these changes will be useful for live coding as well!
Hi all - Recently got my Teletype and I’ve been playing around with 2.3 beta 1 for a few days.
I’m not sure if this is the correct location to post ‘bugs’ - please let me know and move if not.
My PARAM value is fluctuating. I noticed this was reported on an alpha of 2.2 (by @laborcamp) - but looks like it was declared fixed.
I have tried Firmware versions 2.1 release, 2.2beta1 and 2.3beta1. PARAM fluctuates on all of them. I have calibrated (to 0 and 16383 succesfully) . I have tried different power rail and case. It is varying enough to cause me to overwrite the wrong Scene when saving.
I have had a few instances where pressing ALT + UP on a script, to move a line of code, has caused the screen to go blank and require a power cycle.
yes, please post bugs here, unless it’s something 2.2 specific in which case it should go to the 2.2 thread (thanks for testing with multiple version - that’s very helpful!). if it’s a bug that existed before 2.2 then we can add it as an issue on github and it’ll get fixed when one of the developers chooses to work on it.
for the PARAM issue i believe that’s always been that way, there is a small amount of noise on the knob, calibration won’t fix that. i don’t think it was ever fixed, at least not to my knowledge - can you post a link to the discussion? regardless, i think there might be a way to reduce the jitter for scene loading/saving, i’ll think about this one.
Alt-<up> - when does it tend to happen? single line / multiple lines? any other details?
Here is @laborcamp mentioning the PARAM wobble on 2.2 - not sure if it is the same issue:
Personally, I wouldn’t mind losing some resolution on the PARAM knob if it meant it was stable. I have been using it to window through sections of CHAOS - which only really works when it is rock solid!
Regarding ALT + UP. It is almost certainly single line - I’ll try to replicate it. As the screen goes blank suddenly and unexpectedly, I can’t see exactly which line I was on but it has happened 3 or 4 times and each time I had my fingers on ALT + UP!
The commented-out status of a line doesn’t move with the content of the line you are moving.
Moving empty lines between lines of code can break the page such that code is pushed down off the page - ie it appears that an empty line is inserted each time you try to ALT + UP or DOWN to move a line of code.
re: losing resolution on PARAM - you can already do that by dividing or scaling. but sometimes you want a bigger range, so it’s always going to be a trade off. for scene selection my idea is to introduce “dead” zones between values, so even with jitter it shouldn’t change values when it happens to be right on the edge between two values.
moving lines - i’ll go over that code again and introduce some additional boundary checking, so at least it won’t crush. i’ll do that and check the other issues (and the loop issue) tomorrow.
thanks for your help with testing, very much appreciated! i’m a bit surprised tbh there hasn’t been more feedback, it’s been out for a couple of weeks now.
Yes range of 32 works fine as is but I thought you were suggesting dead zones as a fix for jitter at the maximum, non-scaled range. (I would prefer stability at a range of 1024 at the very least! Ideally 4096.)
I must have skipped the section of the pdf where CTRL in the Tracker was mentioned. I’ll double-check any further bugs! Cheers!