Scratch

SeptimusHeap wrote:

nXIII wrote:

SeptimusHeap wrote:

What are the ()s and selfs for?

self is the receiver of whatever message you are sending (the function). Just putting the message wouldn't work, it would say 'message not understood'. The ()'s are to help with layout, because if you put
self pointToX: self getVar: 'blah' y: 0.
it wouldn't work because 'pointToX:getVar:y:' isn't a message, whereas with
self pointToX: (self getVar: 'blah') y: 0.
the messages are 'pointToX:y:' and 'getVar:'.

@Sep:
You aren't defining a new message (well, you're defining doIt and doitIn:, but let's not get into evaluations and contexts), so don't put the message name at the top. For example, your 'grab patch from screen' block would look like this:
___________________________________
grab from screen                |  -       |
-----------------------------------------------------
grabFromScreen.
^ self (optional, automatically included)
____________________________________
...

It doesn't work. Is there a special place to put the image? I just put it in the Panther1.1 folder after deleting Panther1.1.image.

Sorry, it's 'self grabFromScreen', and it can only be sprite-specific because the grabFromScreen method only belongs to ScratchSpriteMorph. And for some reason, the block itself doesn't work for me.

New idea:
I am going to slightly change the 'add a block...' in the block editor and make the base menu ask 'Stage', 'Sprite', or 'All' and supply the blocks for the selected class.

MathWizz wrote:

If you make a block called 'var %s' how do I read the value of %s?

Do you mean with CYOB?
If so, use 't'+[argument number], i.e. 't1' or 't4'. I might change this to 'arg1' or 'arg4'.

Since you're working on 1.2, could you release 1.0?

Oh, OK. What about a private beta?

Sorry if I'm a bit annoying, just because I'm very excited.

I just had a neat idea, how hard would it be to connect Panther to the printer? we could get it to directly print out the stage or a grabbed section of the screen... with printer setup options, obviously as a block that quickly shoots out 100 copies of the stage isn't just annoying, it's expensive.

Did you know?

Color blocks can fit in dropdown lists, like for broadcasts!

Sparks, at this point with 75 pages who would be reading the first post?

What would be the code for a 'delete costume' block?

SeptimusHeap wrote:

What would be the code for a 'delete costume' block?

Sadly, it's not as easy as this.... I looked at it, and the delete button next to every costume has an instance of the class CostumeMedia or something as its receiver, NOT ScriptableScratchMorph. I think the only way to do this is make a new message that looks at all of the sprite's costumes and collects them into a dictionary.

sparks wrote:

hey nXIII, you're on early! I'll take this oppertunity to mention some things:

how useful do you think the printer connection for Panther would be? with better pen blocks, people might start making more art projects.

can we have a fps reporter, there's already an morph in the world menu so it shouldn't be hard, and it might allow projects to skip graphics if it's a slow fps to customise the experence for every computer.

the date time blocks work now, but the date option still reports false in an = block.

any luck getting the scratch cat image replaced with the Panther logo for the EXE file?

could you describe what kind of thing would go into a skin design, as it seems to be quite popular.

Hi! I'm on early 'cause I have today and tomorrow off!

I STRONGLY recommend not making printer connection available due to viruses:
- constant spewing out of pages is, as someone said before me, not only annoying but costly.
- a way to get around a warning: show a dialog that says "The following printer operations are to enable the screenshot feature. Please click 'Always' to allow the screenshot feature to function properly; next thing you know it's in an infinite loop that has hundreds of identical blocks in a hidden sprite that are all printing.

FPS reporter - I believe that the Scratch stepping doesn't have much to do with the world stepping, so the method in the morph wouldn't do too much for you.

Yea, sorry, that's my old solution; I need to make it the new solution.

No

The problem with the skin design is that you have
A) Around 275 images
B) A bunch of background colors set in the code
This means that not only would people in the competition have to design a ton of images, they would have to be good enough at modding the source to figure out every single background color that needed changing, and would have to change it to test it.

sparks wrote:

so should I remove the skin idea from the Panther site? It would have been nice 

No, I'm not saying it shouldn't be there, it would just be a lot of work to make a skin.

sparks wrote:

right. maybe in a second release or something, a folder with the skin items in it, and instructions for changing the background colours? I'm wondering if each skin is a couple of hundred images, that would make a pretty big folder for Panther, so if anything, people would have to be able to choose a skin they like from the site, and install it.

Well, actually, the skin is embedded in Panther already, so you could just have images like 'Panther.image', 'Sparkly.image', 'Monochrome.image', or embed each skin in a dictionary in ScratchFrameMorph so one could switch between them while using Panther. The folder is there so I can reload the skin if I change anything.