Scratch

What am I saying? I always think control is the first category for some reason. Motion. I'm going to test this out in the Scratch > motion section of the library first (unless you've just done all the control ones and want to do that one    )

That's pretty cool! (I still can't get the patch to work on my Scratch    maybe an earlier version of the patch that I ran through wrong has interfered...)

Greenatic wrote:

Debugging Time!   

For Create Arg, the selector given in this part:

Code:

ChoiceArgMorph new getOptionsSelector: #graphicEffectNames;
         choice: 'color'

...will be placed in a "Message not understood" error, without the first letter (i.e. raphicEffectNames).

Having created a custom arg, the above-mentioned error message appears whenever one tries to make a new block.

Selecting 'cannot become watcher' has no effect.

Blocks created in non-expert info have no block info and report "Error!".  They suffer errors when exported, removed, edited, or used as templates.  Selecting "remove icon" on these blocks results in the error "subscript is out of bounds: 0".

Selecting 'view block info' on these blocks and responding to the yes/no prompt causes the following:
If yes selected: error "_______BlockMorphs are not indexable"
If no selected: error "selector not found"

Changing between normal/stop blocks requires refreshing the block palette for the appearance to change.

Thanks for testing, I will fix these glitches. It's nice to have people like you around.

Sparks, could you host a text document (plain text) on some url, which the block importer would update from?

Squawkers13 wrote:

dreamod wrote:

rookwood101 wrote:

Where can we download the latest version of the patch?

It's on my project 'Block Importer 2.0'

it dosent work AT ALL!

What do you mean?

I recently added a thing to the patch, so that when you select 'help' on a custom block it shows the first comment in the block code.

Greenatic wrote:

"reinitializing custom block specs" blocks have Link Errors (i.e. glitches mentioned above).  Adding blockspecs doesn't seem to make the blocks show up.

Why did I even make those in the first place? I'll just remove them.
What do you mean by "Adding blockspecs doesn't seem to make the blocks show up."

There is now an arg translator, it's easy to add your own translations as well. It works similar to the block specs. here is a 'arg translation spec':

($s 'String')

It's pretty self explanatory if you ask me.

Greenatic wrote:

dreamod wrote:

Greenatic wrote:

"reinitializing custom block specs" blocks have Link Errors (i.e. glitches mentioned above).  Adding blockspecs doesn't seem to make the blocks show up.

Why did I even make those in the first place? I'll just remove them.
What do you mean by "Adding blockspecs doesn't seem to make the blocks show up."

I created a block, but it didn't show up.   

Now adding a block made a syntax error:

CommandBlockMorph   as yet unclassified     <none>
^ Array with: #Unmatched parenthesis ->('Sprites' 'control' ('command spec' #- #Test) with: '^ self'

It seems self-explanatory what the problem is here.   

Unlike the usually block spec, this one has extra information. the block spec is included in a bigger spec with the category and wether it's for sprites or not. So it has to end with two parentheses.

Greenatic wrote:

dreamod wrote:

Greenatic wrote:

I created a block, but it didn't show up.   

Now adding a block made a syntax error:

CommandBlockMorph   as yet unclassified     <none>
^ Array with: #Unmatched parenthesis ->('Sprites' 'control' ('command spec' #- #Test) with: '^ self'

It seems self-explanatory what the problem is here.   

Unlike the usually block spec, this one has extra information. the block spec is included in a bigger spec with the category and wether it's for sprites or not. So it has to end with two parentheses.

That was my point.      Is the bug fixed?

That's not a bug. You're supposed to have two parentheses.
('Sprites' 'control' ('command spec' #- #selector))

Squawkers13 wrote:

dreamod wrote:

Squawkers13 wrote:

it dosent work AT ALL!

What do you mean?

i downloaded it but how do you use it?

You copy the code (it's invisible) from the loose 'say %s' block.
Then you copy it into the workspace and file it in. If you can't do that, than wait about a week for the block importer 2.0 image.

dreamod wrote:

Greenatic wrote:

dreamod wrote:

Unlike the usually block spec, this one has extra information. the block spec is included in a bigger spec with the category and wether it's for sprites or not. So it has to end with two parentheses.

That was my point.      Is the bug fixed?

That's not a bug. You're supposed to have two parentheses.
('Sprites' 'control' ('command spec' #- #selector))

Oh, my bad.  I assumed I had typed it correctly.

However, my blocks still aren't appearing in the palette.  No errors are given.

dreamod wrote:

Greenatic wrote:

dreamod wrote:

That's not a bug. You're supposed to have two parentheses.
('Sprites' 'control' ('command spec' #- #selector))

Oh, my bad.  I assumed I had typed it correctly.

However, my blocks still aren't appearing in the palette.  No errors are given.

this could be caused by 'broken' arrays. Which somehow are split into symbols and strings which are used to change the category while generating blocks in the ScratchViewerMorph. That also means they're not block specs. The best way to get rid of this is to 're-initialize CustomBlockSpecsDictionary'.

That fixed it.  Thanks!