Hi,

I got a problem with the makecode editor, you may help me with.
When I use the "on start" and the "forever" Blocks, the code from the "on start" is executed before the code within the "forever"-loop. As the code gets longer, it becomes a real issue, beacuse the "forever"-loop isn't executed at all.
Switching to the JavaScript, I can change the order of the code. As long as the code in the loop "basic.forever" is on the beginning, everthing works out.
But as soon as I switch back to the Blocks, the order is changed again and the program does not execute properly.

Is there a reason for the order that I don't see?
Thank you!

The sharing of beta files doesn't work right now.
The generated link is headed to the normal environment and that can't open the beta file, because it needs the 2.1.48 target version.

I thought it was a hosting-problem of makecodebeta.calliope.cc, but then I found the bug in the other makecode editors. Somewhere in the latest makecode or pxt-updates the capitalization was killed:

microsoft/pxt-arcade#1691

Hi,

I am constantly facing the following error while running pxt serve.
I have checked yotta already as it was mentioned by a similar error report.
Any idea on what can be the root of this problem?

building sim...
[run] cd sim; node ../node_modules/typescript/bin/tsc
log strings: 66 files; 0 strings -> sim-strings.json
building target.json in /home/....../pxt-calliope...
building libs/core
  skip native build of non-project
building libs/radio
  skip native build of non-project
building libs/devices
  skip native build of non-project
building libs/bluetooth
  skip native build of non-project
building libs/blocksprj
*** yotta target calliope-mini-classic-gcc
INTERNAL ERROR: Error: spawn yotta ENOENT
    at _errnoException (util.js:992:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)

When loading an extension the subcategories can´t be localized:

On makecode for microbit the same extension works correct:

Using the Event bluetooth.OnUartDatareceived I get an Error

The Pins P0, P1, P2, P3 should be marked when high and the analog/digital values should be displayed at the correct place. ( The other pins on the Expansion-port should be marked, too when they are used)

When loading Extensions with a .cpp - file,
(like https://github.com/ferenc-hechler/pxt-remember-int)
an error in math.ts appears
Fehler: pxt_modules/core/math.ts(1,1): error TS9043: The hex file is not available, please connect to internet and try again.
The simulator doesn´t load and the program can´t be compiled.

When testing https://github.com/microsoft/pxt-microbit-buttons on my Calliope Mini, I discovered that the file pinscombat.ts in the directory core is missing.

If you create an extension and create a release it ends in an error because of missing pxt-calliopemini

When using devices I get 16 Errors because of double identifier in devices and core/enum.d.ts.
I pasted devices/enumd.d.ts into main.ts and there you can see the 16 double identifiers. It´s in MesDpadButtonInfo

Can we expect a revamp of the pxt-calliope editor in the near future like the one the pxt-microbit editor received recently?

Menu Reference and menu Hardware don´t exist.

The newest releases are not available at https://makecode.calliope.cc/beta as I would expect.

The beta.ref file exists and has "appref": "v", so I thought every release should get deployed on the website as beta.

Since there are a Issues like #59 and #57 which seem to interfere with the hosting it would be great, if we would have the newest releases on the Microsoft hosting as beta.

The pins C16 and C17 don´t appear for serial connections!
So I can´t use and update my ESP-Extension

You still need to be logged in at Github if you want to load an extension.
Tutorials using extensions don´t work, too.

When opening German version of MakeCode within a WebView of an App (on iOS) I see the string „show leds“ in German. However, when directly surfing to it on the same device and same language settings the English version is displayed.
On a desktop, if I have a session open for a very long time I see the blocks „on Pin pressed“ in German as well, but when refreshing the page it is displayed in English!

@importGoogleFonts: true which means this repo is using Google fonts CDN which is against MS security policy.

We need to bundle the font into our CSS instead.

We have Problems using the neopixel library because of missing math functions.
As a workaround we have to add

// notwendige Funktionen für das aktuelle Neopixel-Paket
namespace Math {
export function idiv(x: number, y: number) { return x / y }
export function round(x: number) { return x }
}

So I think we need this two functions in makecode ;-)

When you change those blocks to Javascript

... and change something in Javascript. (add a return)
and change back to Blocks you get errors:

The old Extensions for Calliope Mini like RGB-Colorsensor or calliope BC95 are missing. The Grove Extension v0.1.5 is outdated (v0.1.7).
The Servo Extension would be nice, too.

• APIs
• simulator support

Already translated commands are not shown within the blocks (in German), they are still English and the following error can be found within the console.

Setting the RGB-Led to White makes it light up red.

Circuit playground has a microphone, too. You can change the value for loudness in the simulator like the lightlevel or temperature. So it would be nice to have this for Calliope Mini!

And the way to read the values of the microphone is a little bit difficult/inkonsequent for children. You know Calliope Mini is designed for Children at the age of 9 years. So it would be better to add a loudness Block in Input instead of reading an analog Pin and search the Button for the microphone.

Thanks! Michael

Initially loading pxt.mini.io or pxt.mini.io/beta does not render the Calliope preview.

When I try to delete files sometimes the errormessage This project is already opened elsewhere appears. But it isn´t opened elsewhere.

Describe the bug
In the new hardware version (Version 1.3). The MIC values seem random. There is no accurate read.

To Reproduce
Steps to reproduce the behavior:

Simply screen the pins.analogReadPin(AnalogPin.MIC) .
The numbers vary between 480 and 530

Expected behavior
It should reflect the noise around. Simply attach a previous hardware version and see

Additional context
I am not sure if it is something that can be done through software changes. is it simply a production bug?

When using German as main language the link to tos is https://www.microsoft.com/de-de/corporate/rechtliche-hinweise/nutzungsbedingungen.aspx though it seems like the following url should be the right one:
https://www.microsoft.com/de-de/rechtliche-hinweise/nutzungsbedingungen

• simulator support
• blocks / JavaScript

The following packages doesn't work anymore, though they did at least with PXT:
https://github.com/calliope-mini/pxt-calliope-esp
https://github.com/calliope-mini/pxt-calliope-bc95
Error tracing is quite hard as they don't appear in the logs.

Please include more languages (most important): Spanish, Portuguese, Japanese, Russian, Ukrainian, Arabic...

it is impossible to login into Github with the updated Version.

Right after complete installation, i try to export a static version. I face the following error.

INTERNAL ERROR: TypeError: Cannot read property 'replace' of undefined
at Object.renderMarkdown (~/pxt-calliope/node_modules/pxt-core/built/pxt.js:58949:33)
   at renderDocs (~/pxt-calliope/node_modules/pxt-core/built/pxt.js:81652:33)
   at ~/pxt-calliope/node_modules/pxt-core/built/pxt.js:83305:34
   at tryCatcher (~/pxt-calliope/node_modules/bluebird/js/release/util.js:16:23)
   at Promise._settlePromiseFromHandler (~/pxt-calliope/node_modules/bluebird/js/release/promise.js:512:31)
   at Promise._settlePromise (~/pxt-calliope/node_modules/bluebird/js/release/promise.js:569:18)
   at Promise._settlePromise0 (~/pxt-calliope/node_modules/bluebird/js/release/promise.js:614:10)
   at Promise._settlePromises (/~/pxt-calliope/node_modules/bluebird/js/release/promise.js:694:18)
   at Promise._fulfill (~/pxt-calliope/node_modules/bluebird/js/release/promise.js:638:18)
   at Promise._resolveCallback (~/pxt-calliope/node_modules/bluebird/js/release/promise.js:432:57)
   at Promise._settlePromiseFromHandler (~/pxt-calliope/node_modules/bluebird/js/release/promise.js:524:17)
   at Promise._settlePromise (~/pxt-calliope/node_modules/bluebird/js/release/promise.js:569:18)
   at Promise._settlePromise0 (~/pxt-calliope/node_modules/bluebird/js/release/promise.js:614:10)
   at Promise._settlePromises (~/pxt-calliope/node_modules/bluebird/js/release/promise.js:694:18)
   at Promise._fulfill (~/pxt-calliope/node_modules/bluebird/js/release/promise.js:638:18)
   at MappingPromiseArray.PromiseArray._resolve (~/pxt-calliope/node_modules/bluebird/js/release/promise_array.js:126:19)

appearantly this has been an issue before microsoft/pxt#3612, but i did not get any info on how was is solved in microbit.

In Javascript Mode the preset Pin P0 isn´t an analog Pin at the Calliope Mini. Please use P1. Only ServoSetpulse is correct.

makecode.calliope.cc Version: 2.1.45
Microsoft MakeCode Version: 5.32.21
Laufzeitumgebung calliope Version: pxtgc-0

Describe the bug
The submenu "...more" (...mehr) in the blocks menu is not working any longer. The presented blocks stay the same. So you cannot access the additional blocks.

To Reproduce
Steps to reproduce the behavior:

1. Go to https://makecode.calliope.cc/beta#editor
2. Click on e.g. 'Eingabe' (input blocks are shown)
3. Click on '...mehr' (blocks don't change)

Expected behavior
Clicking on a '...more' submenu should show the additional blocks.

Screenshots

Desktop (please complete the following information):

• OS: Win7 Prof.
• Browser: Firefox
• Version: 72.0.2 (64 bit)

I think you forgot implementation of turnrgbledoff in the simulator:

Or you remove it, it´s not necessary.

Hm, show number doesn´t work any more in simulator. Only LED(0/0) is blinking

• add SVG elements in simulator
• map pins in pxtarget.json

Testing my new extensions I discovered that they stay in german even when I switch to english. Same Error with other extensions like Neopixel

@Amerlander : In pinscompat.ts shouldn´t P3 better be PWM instead of AnalogPin?

• APIs
• simulator

It seems that old hex files can't be opened in the new version of MakeCode.
Attached are two previous versions generated that can't be opened in the current version.

Hex.zip

Not really a bug but the color on advanced is badly chosen for easy reading.
Or am I just getting old?

To make the dialog look better, add a icon.png in each repo.

staticpkg problem still persists [#31]

However there is already a working version hosted here from Microsoft :
https://makecode.calliope.cc/
How is this possible? is there a way to manually have a short fix for the old version?

Thank you for your time

As a couple of people would liket to host the new version of MakeCode on their own, it would be good to open the repository to the public.

The cards in First steps, Tutorial ... stay blank since the new hosting of calliope beta!

There is no block to turn off the RGB led. Turning it off using the '0' from the 'maths' menu is very counter intuitive.