Hello, fellow nerds!
If you are beginning to look into changing the actual source of scratch, to, for instance, make your own version, then I am certain you will run into some sort of problem.
If so, here is where you can post your question, and I will see if I can help.
Also, if you are Squeak-Savvy yourself, please add to it here, too!
Offline
Good point Pinochio.
Offline
No problema! lol
Offline
pinochio wrote:
i know how to hackin the source code of 1.3 but what about 1.4?
Yh. hav asked jens
Offline
If I am correct, you use Jens' method:
Find a bug, type Preferences enableProgrammerFacilities into the walkback, etc.
And, the problem in 1.4 is, you can't find any bugs, right!
Well, here's what I use:
In the default cat sprite, make another costume to be a single pixel (the colour doesn't matter).
Then, set the sprite to be 54000% in size.
Now, just switch to the cat costume...
You will see a red walkback window entitled 'space is low'
Be sure to delete that offending cat sprite and then set it to 100% soon; those errors are there for a reason.
If by chance it causes a squeak memory dump (denounced by an unflattering text-filled white rectangle in the top left corner) then try it again with a smaller size. (ie: 2000%, etc. 54000 is the largest it will allow for a single pixel)
Please do not advertise this method outside this forum, because if the scratch team gets wind of it, they will be sure to fix it. And we all know how precious these bugs can be.
Offline
billyedward wrote:
If I am correct, you use Jens' method:
Find a bug, type Preferences enableProgrammerFacilities into the walkback, etc.
And, the problem in 1.4 is, you can't find any bugs, right!
Well, here's what I use:
In the default cat sprite, make another costume to be a single pixel (the colour doesn't matter).
Then, set the sprite to be 54000% in size.
Now, just switch to the cat costume...
You will see a red walkback window entitled 'space is low'
Be sure to delete that offending cat sprite and then set it to 100% soon; those errors are there for a reason.
If by chance it causes a squeak memory dump (denounced by an unflattering text-filled white rectangle in the top left corner) then try it again with a smaller size. (ie: 2000%, etc. 54000 is the largest it will allow for a single pixel)
Please do not advertise this method outside this forum, because if the scratch team gets wind of it, they will be sure to fix it. And we all know how precious these bugs can be.
that works. i gave the bug to JSO and he has already made an image with a developer menu.
Offline
JSO wrote:
That's true but I recommend to wait until the Scratch team releases the official source.
AAAAANNNNDDDD when will that be?
Offline
I think that they should leave a couple back doors like this, I mean who would need a 54000^2 pixel character, that changes into a levithan cat
Offline
illusionist wrote:
JSO wrote:
That's true but I recommend to wait until the Scratch team releases the official source.
AAAAANNNNDDDD when will that be?
From previous version, I am guessing about 2-3 months from the release. that would be anywhere from late September to October.
Offline
songhead95 wrote:
I think that they should leave a couple back doors like this, I mean who would need a 54000^2 pixel character, that changes into a levithan cat
You are correct in the latter assumption... But the thing is, this can very well crash scratch. I have tried a number of other things like this, such as an uber-huge scrolling terrain in an RPG, and that brought up this walkback, too. On other occurrences, scratch has crashed. If the two were combined, then everything I'd done on the game since last save would be lost. And considering the relative ease of closing up this bug, I think that the scratch team will find it worthwhile to do so. Also, this is the only 1.4 bug that me, and many other scratchers are aware of... it may be the only one. And like any software developer, I can see why the scratch team would want a "Perfect Scratch."
Offline
Hi billyedward.
I just want to have a look at the scratch source code on a windows machine. I downloaded the source code image file and a copy of Squeak but the environment is totally alien to me and I could not find a way of opening up the source code files. It would be useful if you could tell us how to you open up the source files on Windows.
Thanks...
Offline
redware wrote:
Hi billyedward.
I just want to have a look at the scratch source code on a windows machine. I downloaded the source code image file and a copy of Squeak but the environment is totally alien to me and I could not find a way of opening up the source code files. It would be useful if you could tell us how to you open up the source files on Windows.
Thanks...
To run the image, drag it onto a scratch executable.
To actually edit the source code, use the green 'browser' window.
I think that you are talking about the first one...
Reply if not.
Offline
For awhile I have been attempting to write the coveted 'Hide list' and 'Show list' blocks. any ideas
Offline
pinochio wrote:
i know how to hackin the source code of 1.3 but what about 1.4?
i know hacking 1.3 source 2 !
Offline
songhead95 wrote:
For awhile I have been attempting to write the coveted 'Hide list' and 'Show list' blocks. any ideas
i can tell you a code 4 this !
Offline
('hide list %L - hidelist:)
('show list %L - showlist:)
i think
Offline
dav09 wrote:
('hide list %L - hidelist:)
('show list %L - showlist:)
i think
Yes, but are hidelist and showlist already defined in the source code?
Offline
no they aren't, I know how to do THAT part. I was looking into defining a new method for show/hideList:
Offline
songhead95 wrote:
no they aren't, I know how to do THAT part. I was looking into defining a new method for show/hideList:
that is the method !
Offline