#61

Is it possible that my turtle was blocked on the bottom left corner ?
Also, are we supposed to set @WRAP 1 or just @WRAP ?

#62

Aaaah, maybe there is a typo, isn’t it supposed to be

@F x1 y1 x2 y2 rather than @F x1 x2 y1 y2 ?

#63

If you find a script that seems to misbehave, share it and I’ll check.

And it’s @WRAP 1.

Typo fixed, thanks!

1 Like
#64

this is great, thank you. just checking that you’re updating the CHANGELOG on your branch with these changes?

interpolation is great, for sure. but it’s not returned by default with @ correct? it’d be better to have not a mode switch, but just a separate op that returns the interp value ie @INTERP

2 Likes
#65

It would be more coherent to some of other TT syntaxes, indeed.

#66

Whoops! I’ll edit my commit messages into there.

#67

The PDF from your beta5 branch is building fine on my Arch Linux system. Haven’t tried it on OSX, but I assume it’s fine there too. Let me know if you need some more help.

A few little things that I noticed…

For this commit:

You probably wouldn’t have seen in the PDF, but you’ll need a blank line before the

## v2.0

in the change log to get it to render properly (GitHub flavoured Markdown vs Pandoc Markdown…)

For this commit:

You’ll want get rid of this change, otherwise when you merge, the Travis icon will be for your branch rather than upstreams.

#68

Glad to hear the docs build fine :slight_smile: Guess I have to actually do the reinstall of pandoc like I said I would

Thanks! Will change that.

Yes, I was planning to roll that back.

1 Like
#69

@Leverkusen here’s a 2.0.1 beta with the screen glitches fixed (at least my initial stress tests show as much).

simply updated libavr32 with the fixes from @scanner_darkly and made any changes needed to get it compiling. looks good.

if anyone else could test prior to me posting this up on github, i’d appreciate it. then @sliderule can close out his new batch of features.

teletype-2.0.1b1.zip (104.9 KB)

if someone can torture this with i2c as well, that’d be helpful.

10 Likes
#71

I am a bit short of time at the moment but just flashed 2.0.1b1 and two patches that had given me a lot of glychees over the last days seem to work fine at a shot glance when randomly skipping through the modes and scripts, which got me to a lot of unreadable lines before.

The patches/scripts also make use of i2c remote for classic meadowphysics and all four TXo oscillators.

So no hard tortures possible yet but seems to look good.

:slight_smile:

6 Likes
#72

Well, I only just finished writing a better test framework, so my next build won’t be until tomorrow, but it will only contain turtle fixes and more testing.

My weekend got bogged down in 3D modelling and printing parts for everything on the honey do list, then my server administration job had a 8 hours of unexpected work. Soooo… tomorrow night!

2 Likes
#73

i’ll get the merge together then. you shouldn’t have any conflicts pulling it into your branch.

1 Like
#74

Alright. The new testing framework is not revealing anything new, and I’d like to do some refactoring on it, so here comes beta6, up-to-date with monome/teletype/master.

Bug Fix: sin() wasn’t working properly. Now it is :smiley: @STEP now works as expected in all modes and at all directions.

teletype-2.1.0-beta6.zip (421.8 KB)

2 Likes
#75

Saw the screen glitch for the first time, thought the bug wasn’t fixed. Was running a pre-merge build. Uploaded new build, can’t get it to glitch again. :+1:

Here’s a turtle setup that I enjoy. It’s an edge-triggered bouncing note sequencer, a pretty basic use case. Populate the pattern grid (0,0,1,4) with your favourite intervals, patch in a slow random gate to 2 to modulate the pattern.

I: @F 0 0 1 4
   @DIR 35
   @BOUNCE 1
   @SCRIPT 1
M: @STEP
1: TR.P 1; CV 1 N @ 
2: @DIR + @DIR 170
6 Likes
#76

Here’s an easy implementation of @SHOW

4 Likes
#77

Bug Detected!

You can access the temp script by cycling through scripts with [ and ]. Easy fix.

1 Like
#78

is that the semicolon script? i was wondering…

#79

Indeed it was. It gets used to carry the originating script number from delayed commands, as well as processing live commands with an execution context to permit the new L behaviour.

#80

Regarding @SHOW…

I currently display the @ symbol on the right hand side of the cell. Right now there’s a bug where when it’s in the right hand column, the graphic wraps the screen by 1 pixel due to @`s width, so it needs to be corrected, which will actually be quite kludgey with my limited knowledge of the graphics library.

There are options, however. Here are some I’ve thought of:

  • Display it on the left side, which is somewhat obfuscated given that the pattern details are on the right side
  • Display it in the middle of the cell brightly, obscuring part of the value
  • Shade the current turtle cell in the middle
  • Shade the entire turtle cell

Thoughts?

#81

Might be a stupid question but what is an semicolon script and a temp script?