nXIII wrote:
I can work on making the watchers update only when their values change (with a maximum refresh rate)
they're supposed to already do that (don't update unless their values change). Aren't they?
Last edited by Jens (2012-01-15 15:45:42)
Offline
Jens wrote:
nXIII wrote:
I can work on making the watchers update only when their values change (with a maximum refresh rate)
they're supposed to already do that (don't update unless their values change). Aren't they?
Yes, but they could update immediately when their value is changed if they were notified of the change
Offline
Jens wrote:
. Wait, twice per second that's faster than my wristwatch
the stopwatch on my watch has milliseconds
Offline
I just found this post:
fanofcena wrote:
BYOB is always 1 step ahead of scratch
scratch 1.4 - byob 2.0
scratch 2.0 - Byob 3.0
with all the cool new features BYOB Will soon become a pros language for experimentisation
Now, it's 2 steps ahead
Offline
bharvey wrote:
Update: We made some significant decisions, and there's a bunch of new code coming very soon... Watch this space...
Eagerly awaiting the changes...
Offline
Do you guys think I should ask the mods to change the title of this thread to "Snap! - Discussion Thread"? Or "BYOB 3 / Snap! Discussion Thread"?
Offline
Lucario621 wrote:
Do you guys think I should ask the mods to change the title of this thread to "Snap! - Discussion Thread"? Or "BYOB 3 / Snap! Discussion Thread"?
Yeah... Nobody actually talks about BYOB 3 anymore.
Offline
Lucario621 wrote:
Do you guys think I should ask the mods to change the title of this thread to "Snap! - Discussion Thread"? Or "BYOB 3 / Snap! Discussion Thread"?
Actually we're thinking that when we have an official beta release we'll start a new thread, so people who are just learning about it don't have to wade through a bazillion old messages.
Offline
bharvey wrote:
Lucario621 wrote:
Do you guys think I should ask the mods to change the title of this thread to "Snap! - Discussion Thread"? Or "BYOB 3 / Snap! Discussion Thread"?
Actually we're thinking that when we have an official beta release we'll start a new thread, so people who are just learning about it don't have to wade through a bazillion old messages.
OK . And of course, you can have the honors of starting that thread .
Offline
I don't think you have to ask moderators to change the title of a thread. I thought it was as simple as clicking edit on the original post.
EDIT: Oops, I guess not.
Last edited by shadow_7283 (2012-01-17 18:02:56)
Offline
shadow_7283 wrote:
I don't think you have to ask moderators to change the title of a thread. I thought it was as simple as clicking edit on the original post.
EDIT: Oops, I guess not.
You can only edit the title within the first 10 minutes of posting the thread.
Offline
Hi, I have the following problem (BYOB 3.1.1):
I use variables on the screen to realize a dynamic text output function (presenting the content of the variables in the "large readout" mode). But if I save my project some variables will reset: they are in the "normalreadout" mode an on an other position I gave them befor saving. Is there any way to set the position of shown variables via script? Or what else can I do to force the variables to their right screen position.
Thanks for any help!
Jens
Offline
dianoia wrote:
Hi, I have the following problem (BYOB 3.1.1):
I use variables on the screen to realize a dynamic text output function (presenting the content of the variables in the "large readout" mode). But if I save my project some variables will reset: they are in the "normalreadout" mode an on an other position I gave them befor saving. Is there any way to set the position of shown variables via script? Or what else can I do to force the variables to their right screen position.
Thanks for any help!
Jens
This is a problem in Scratch, and it seems it carried into BYOB. Just save the project with the variables set the right way, and showing.
Look, something about BYOB3! XD
Offline
scimonster wrote:
Just save the project with the variables set the right way, and showing.
Thanks, but it only works with variables in normalreadout - not in large readout mode. I think I have to work with the "say" command to get all things probably displayed. Or I wait for Snap! Is there an import/export function in the prealpha?
Jens
Offline
Hmm. I was just google searching BYOB for the fun of it, and I was surprised to find that there is a wikipedia article on BYOB. Not as awesome as the Scratch Wiki article though .
Offline
Lucario621 wrote:
I was just google searching BYOB for the fun of it, and I was surprised to find that there is a wikipedia article on BYOB.
Ah, thanks for pointing that out. It's pretty recent. The person who wrote it is also the one who told me I should send BYOB to CNet download.com.
Offline
http://chirp.scratchr.org/dl/experimental/JsMorphic/history.txt wrote:
120119
------
* MOD, TRUE and FALSE reporter blocks
* AND, OR, NOT reporter blocks
* BROADCAST AND WAIT command block
Only the string operations and math functions, an you're done with the green ones
Offline
roijac wrote:
* MOD, TRUE and FALSE reporter blocks
* AND, OR, NOT reporter blocks
* BROADCAST AND WAIT command block
Nobody seems to have noticed the even more important previous change, in which plus signs for modification were added to custom block prototypes. Right now they're a subtle grey-on-grey; too subtle, I guess, since nobody noticed! Maybe, Jens, an orange plus but no circle around it would be subtle enough but not too subtle?
(The original idea about the orange circles was that they look like the orange variable blocks that they're used to add. Maybe /that/ was too subtle?)
Offline
roijac wrote:
do you think it's more important? oh well ^^
Well, the primitive blocks are mostly trivial to implement (the exceptions are the ones like GLIDE that interact with thread scheduling); it's just a matter of getting around to them. The plus-sign thing is important to me because it's a new UI experiment; unlike the old ones that came in pairs, these are single plus signs that you use by aiming between words, avoiding all that shifting around as you mis-aim slightly in the old UI.
Offline
bharvey wrote:
roijac wrote:
do you think it's more important? oh well ^^
Well, the primitive blocks are mostly trivial to implement (the exceptions are the ones like GLIDE that interact with thread scheduling); it's just a matter of getting around to them. The plus-sign thing is important to me because it's a new UI experiment; unlike the old ones that came in pairs, these are single plus signs that you use by aiming between words, avoiding all that shifting around as you mis-aim slightly in the old UI.
I like the new UI!
Offline