Open tballmsft opened 2 months ago
hmmm... yeah referencing variables defined in other files is not supported today. i'm also not sure it's such a great idea, what if the user creates their own screen variable? will it override the default screen or will it be pointing to some variable that the user might have no knowledge about?
i think it would be safer to just define a screen()
function with a block and use that as the default.
in microsoft/pxt-arcadeshield we have a global variable screen: Bitmap. I want screen to be the default variable used in blocks, which is accomplished using the bmap.defl line below
However, the compiler thinks I am trying to add a new variable screen and does renaming, so I get:
instead of what I want