#5

Alright, got it installed. It froze on the initial auto-reboot, but shutting down my modular fixed it.

USB loading worked on the first try!

1 Like
#6

Was it just a blank screen? And could if you can remember how long you waited until you power cycled.

Thanks for reporting back.

#7

Installed ok for me, but it didn’t seem to recognise the keyboard until after a restart. USB worked first time after that restart.

1 Like
#8

That’s expected, it’s to do with how the USB works, it won’t switch from device to host without a reboot. One day I’ll make it so that it will switch without a reboot…

I’ll update the instructions at the top.

#9

Not sure what changed in the beta for USB read/write, but can we change it so it doesn’t overwrite existing save files on bootup? I went through the update procedure for 1.4.0 last night, and forgot to change the filenames for my backup scenes… and then lost all of them when they overwritten by the default scenes :frowning:

Luckily I think I have everything documented in my posts here on lines, but it was definitely a bummer.

1 Like
#10

How do people feel about merging the tilde (~) key with TAB?

At the moment TAB switches between editing scripts and the live page. And tilde switches between tracker and where you were before.

Instead TAB could rotate between live, edit and tracker.

3 Likes
#11

Eeeek. It’s not supposed to do that. And I have no idea what could have changed it to do that either. I’ll investigate this evening.

1 Like
#12

I’ve had a look at the code and the docs, I believe that’s the intended behaviour, and it’s always worked this way:

Insert prior to power-up, then power-on the module. All scenes in flash will be written TT??S.TXT to the root, where ?? is the scene number (00-31). Any files labelled TT??.TXT will be read to flash at the scene position ??.

source

The code always writes to tt??s.txt files, and will only overwrite the Teletype internal memory with tt??.txt files.

I’ll add a warning at the top about USB backup, and I guess we can discuss what the intended approach should be.

#13

No, it showed the live-entry screen but wouldn’t respond to the keyboard. I think it might be similar to what @GoneCaving reported.

1 Like
#14

i prefer the dedicated, quick access to those sections rather than cycling through menus.

2 Likes
#15

i do find i often confuse the tilde key with the tab and vice versa. perhaps an alternative key could be used to switch between live/edit/patterns?

also would be nice if pressing [ or ] while in live mode would take you to editing pages.

3 Likes
#16

Dedicated quick access suggests a desire for zero toggles and three dedicated keys.

2 Likes
#17

I’m planning on adding dedicated hot keys for each of the script editing pages with mod+F1 though mod+F10 (which modifier still to be determined). Maybe we can think of another 2 keys for direct access to live and tracker.

Me too. Which is why I’d like to cycle with tab.

Good idea!

Tomorrow is rewriting the keyboard handling day, though it might take more than a day. Once it’s rewritten it’ll be easier to tweak the keys.

I’ve already deleted the II op.

2 Likes
#18

Sorry, to be clear this was definitely user error on my part – I was running an update from an older version (1.2 maybe?) to 1.4 last night.

But it feels like this is a little too easy to do, I’m suggesting we change this for 2.0 (or some future version)
Maybe TT??S{N}.TXT where {N} increments for each version saved?

2 Likes
#20

Definitely, especially when one of the main uses for USB saving/loading is firmware updates. It’s too easy in such a circumstance to overwrite everything.

1 Like
#21

i’d be very into the rotating through all 3. Jumping between the tab and ~ is frequently a small mind boggle, and i think i always half expect it to just rotate through all 3 anyway

1 Like
#22

Managed to refactor the keypress handling…

It doesn’t actually do anything different yet. But given that is +553 lines, -449 lines of code, I feel the need to tell people about it.

Next up tweak the way we deal with key codes and mod masks.

Then move out the implementation of each event to it’s own function, e.g. updating a pattern, the line editor.

Then maybe actually work on some features! I’m hoping to add some extra keybindings to the line editor too… e.g. C-a, C-e, C-b, C-f, C-h, C-d, C-w, M-b and M-f.

3 Likes
#23

not really related to the keypress handling, but the overall overhaul for 2.0

as part of 2.0, a consolidated ops + keyboard shortcut list with some light explanation on expanded/revised features would be really helpful. The documentation of the sweet incremental work through the v1 versions feels scattered (at least in the web, not sure about F1) through update posts and additional features to the main TT page, and might benefit from some tidying up in a rounded out 2.0 version

I’d happily volunteer to create a revised/expanded v2 .pdf w/ all the revisions, aliases, new ops and updated ii commands and some kind of web documentation if people would find that helpful

7 Likes
#24

Nice! I agree that it should be consolidated.

As a heads up, I’m posting two PDFs and a LaTeX version of Teletype Studies sometime later today. I really wanted a printable copy of those on hand.

6 Likes
#25

will take a look this weekend. confused about this part:

do you mean CTRL+… and MOD+…? what would they do?

1 Like