Scratch

sparks wrote:

do we even know how to change the output file type?

Nope, but nXIII can deal with that.

sparks wrote:

discontinued? ah, that would be why no one knew what I was on about with it then. howzat? would .pnt be a good one?

(AARGH! keep clicking alt S to save a post, dropbox is taking me over!)

Lol, they stoped it on the release of their 7th OS apparently.
And yeah, i still press Ctrl+S sometimes.

markyparky56 wrote:

sparks wrote:

do we even know how to change the output file type?

Nope, but nXIII can deal with that.

Yes, I know how, it's very simple.

LOL! I JUST PRESSED CTRL + S!

sparks wrote:

I thought it would be, but reading it might be a problem?

OMG! I laughed at MathWizz's stupidity, then actually pressed cntrl S without thinking. I was very surprised when the "save" blox popped up O_O

and did it again.

Save BloX?

sparks wrote:

¬_¬ box. I also keep starting a post with "Sparks:" and then having to delete it 

Where's nXIII?

Idk, He'll turn up eventualy.

sparks wrote:

hm. wow! we're nearly on 100 standard pages!

Yep. I wonder if there are any bigger than this...

I wonder how big it would be if it only had posts relating to Panther.

MathWizz showed me this pic it's pretty cool

We now have a <[...v] Recived?> block! Kinda limited though, you could use it for a safety lock to make sure something gets sent before you continue, maybe good for an Email system on an OS? Only works if you have the hat block in the script aswell.

sparks wrote:

markyparky56 wrote:

Only works if you have the hat block in the script aswell.

well that's easily solved (aside from fixing the glitch) just have "when green flag clicked" -> broadcast start and then give all the scripts "when I recieve start" rather than flag hats.

But thats kind of avoiding it, not solving it. I still really want the <When I recive [...v]> block, I have an idea about how to do it aswell, nXIII said about how when the broadcast block is activated, it searches for the hat blocks with the thing to be recived, have it search for <When I recive [...v]> blocks aswell?

sparks wrote:

I think one problem for the <recieve> block is that the broadcast only lasts a short time.

What about like what BYOB does? the launch and run blocks?

Re: <I receive>

sparks wrote:

I think one problem for the <recieve> block is that the broadcast only lasts a short time.

Hey guys, you know, you could (or, if I followed this thread correctly, you already maybe have) implement a "last received" reporter that remembers the last message received by any object. Then you could continuously check if the <last received> message has changed - and there you have it.

Another hint: There's a pretty cool abandoned "WhenHatBlockMorph" in the code that basically allows you to create your own hat blocks by just inserting a boolean. If you just tweak the code a little it works like a charm, plus it's really cool. Then, of course, you could use this in combination with the <last received> block.... (!)

Last edited by Jens (2010-05-11 14:23:56)

Jens wrote:

Re: <I receive>

sparks wrote:

I think one problem for the <recieve> block is that the broadcast only lasts a short time.

Hey guys, you know, you could (or, if I followed this thread correctly, you already maybe have) implement a "last received" reporter that remembers the last message received by any object. Then you could continuously check if the <last received> message has changed - and there you have it.

Another hint: There's a pretty cool abandoned "WhenHatBlockMorph" in the code that basically allows you to create your own hat blocks by just inserting a boolean. If you just tweak the code a little it works like a charm, plus it's really cool. Then, of course, you could use this in combination with the <last received> block.... (!)

Very helpful, thanks, but we don't have a Last  recived block, we just have a boolean block which reports if a broadcast has been recived.