Scratch

Hi Hardmath123,

thanks for the bug report. Turns out it's the same underlying problem that was also haunting the factorial base case. I think I fixed it in last night's update. So if you would like to try again...

Thanks!

P.S. I love the curlicules!

Oh, yes: another bug (well, more glitch then bug) I found this morning. The scrollbar for the blocks is quite weird at times. It can 'catch' the mouse, at which point it crazily starts following the mouse instead of stopping the scroll once the mouse is released. Then you can't do anything except close the window. It gets annoying. It might be better to break them up into categories, or create 'pages' instead of 'lists' of blocks (visualize an iOS home screen with only one column, blocks instead of apps, and a next/previous page button).

EDIT: Did you change anything major? Right now, when I opened up Snap! to try the recursion again, the scrollbar completely gave up on moving. I admit I'm using FireFox (one gets tired of Safari after a few years), which could be the problem.

Last edited by Hardmath123 (2011-10-18 04:31:37)

Jens wrote:

I didn't change anything major. The whole GUI is still just a very experimental pre-pre-pre-alpha one and will change dramatically, including scrollbars and pages. Right now I'm only working on the evaluator and on the syntax elements themselves. BTW you shouldn't have to close the window, even on FF which is slow. Just click on the palette's background and it should stop moving and be responsible again. Thanks again!

That's what I used to do. Now it doesn't work, instead, the scroll keeps following the mouse. 

@bharvey
Snap! : I can't succeed in using recursion for a graphic application like "tree" for example.
Is it possible and how if yes ?

Hardmath123 wrote:

This works in BYOB but not in Snap!
http://www.imgpaste.com/3Vrm.png
EDIT: It's the ()^() block as a variable.
EDIT: Can you add ()^() as a Snap! feature?

Actually, this assumes that the second value is a positive integer.

@ roijac_test
Many thanks, I've made a mismatch between Script Variables and The script variables.
Find attached 3 examples of graph+recursion.

@Jens
I appreciate every compliment coming from you 1 000 000 more amazing than me !
Anyway, it proves that Snap! in its pre-pre-pre-... release has already many interesting capabilities. I'm impressed by its resistance to severe/blocking bugs and its user-friendliness.

Hardmath123 wrote:

Sierpinski gasket:
http://www.imgpaste.com/EJyn.png
Sorry, I gave up on doing it with Snap!, it kept freezing.

even on my beast machine (intel i7 2600k) scrolling is very slow, but most other things are fine.

Because snap! redraws all dirty rectangles, when you move the scroll bar on anything, a lot of things are 'dirtied' so it has to redraw them all, and canvas is not known for being the fastest thing known to man.

I would think that in the future, you could find some other way of doing scroll bar inclusive areas (or at least the block palette) by possibly having a single not-very-often updating canvas, and then using a standard browser scroll bar, to do standard scrolling, instead of using all the canvas redraw stuff.

It sounds quite hard to implement (with all the other bits you would have to change, but I can't think of any other way of doing it. I'm sure you'll come up with something.

Jens wrote:

Hi rookwood101,
actually nothing is "redrawn" at all when you scroll something, but a lot of cached offscreen canvasses are "blitted". We'll speed up scrolling by caching the bitmaps of composite shapes, but right now my priorities elsewhere.

sounds good to me 

Morphic Scrolling Update

Due to popular request I've dramatically sped up scrolling in Morphic and Snap!. Please reload the pre-pre-pre-alpha page in your browsers to make sure you've got the latest version (not the one in your browser cache), enjoy and be awed. 

Last edited by Jens (2011-10-19 10:09:05)

Hardmath123 wrote:

So... it's a no to 'pages' of blocks? No scrolling needed...

The current arrangement with everything in one palette isn't permanent.  We just aren't putting a priority on user interface details until the core functionality is there.

bharvey wrote:

[but grabbing a block from the palette seems to work better -- I no longer have to hold it in place for a second before moving it.     

Was that done after the scrolling, because I was on my mac mini (slow    ) and found that it was requiring me to do that, I reloaded the page and it's fine now  . All is good in the land of slow computers. Now to test on my beast 

edit:    soooo smooootttttthh

Last edited by rookwood101 (2011-10-19 12:39:51)