When I'm in fill-off, I've made some changes and clicked on save&quit, Scratch stops working and looks like this:
I use Ubuntu x64, and this is the first time I edit Scratch, so I don't know when this started.
Please help!
Last edited by roijac (2011-07-12 05:42:38)
Offline
Try forcing it to close (Alt + F4), then opening and reediting it.
Offline
How big are the edits you're trying to make?
Offline
To make it clear, I tried:
save image for end-user (with both fill-on and fill-off)
save (in the dill-off menu)
save&quit (in the fill-off menu)
They all produce the same problem as above.
I tried saving as, but it said there isn't a scratch.changes file and didn't let me.
It's not about editing, it's about saving - it produce it even if I edit nothing and just save.
Offline
roijac wrote:
To make it clear, I tried:
save image for end-user (with both fill-on and fill-off)
save (in the dill-off menu)
save&quit (in the fill-off menu)
They all produce the same problem as above.
I tried saving as, but it said there isn't a scratch.changes file and didn't let me.
It's not about editing, it's about saving - it produce it even if I edit nothing and just save.
Did you try using the close scratch block from the block lib, the one that has the code Smalltalk Quit: true andSaveImage: true. That might work...
Offline
Pecola1 wrote:
roijac wrote:
To make it clear, I tried:
save image for end-user (with both fill-on and fill-off)
save (in the dill-off menu)
save&quit (in the fill-off menu)
They all produce the same problem as above.
I tried saving as, but it said there isn't a scratch.changes file and didn't let me.
It's not about editing, it's about saving - it produce it even if I edit nothing and just save.Did you try using the close scratch block from the block lib, the one that has the code Smalltalk Quit: true andSaveImage: true. That might work...
lol this could work if i could edit scratch
Offline
roijac wrote:
Pecola1 wrote:
roijac wrote:
To make it clear, I tried:
save image for end-user (with both fill-on and fill-off)
save (in the dill-off menu)
save&quit (in the fill-off menu)
They all produce the same problem as above.
I tried saving as, but it said there isn't a scratch.changes file and didn't let me.
It's not about editing, it's about saving - it produce it even if I edit nothing and just save.Did you try using the close scratch block from the block lib, the one that has the code Smalltalk Quit: true andSaveImage: true. That might work...
lol this could work if i could edit scratch
![]()
Oh, you cant edit scratch either? You can always just edit it then save image using it if you can edit. Do you have the code block?
Offline
Don't save that block, just edit it.
Offline
scimonster wrote:
Don't save that block, just edit it.
It HAS to be saved for it to work.
Last edited by Pecola1 (2011-07-12 13:14:20)
Offline
Same thing happens to me. I also use Ubuntu. When I try to save the image, the same thing happens, unless I'm using the Source Code. .-.
Offline
By the way, when that happens, I just use Force Quit. In my version, to get force quit, you just right click on the top panel, select Add to Panel, and choose Force Quit. Then, when you need to force quit something, you just click on the force quit icon from the top panel, and click on the program which you want to close.
Offline
so it seems it's ubuntu problem...
anyone with other linux version this happens to him?
Mcsugarface wrote:
By the way, when that happens, I just use Force Quit. In my version, to get force quit, you just right click on the top panel, select Add to Panel, and choose Force Quit. Then, when you need to force quit something, you just click on the force quit icon from the top panel, and click on the program which you want to close.
i have 11→no panels
Last edited by roijac (2011-07-14 13:04:55)
Offline
Hmmm... it's more likely a x64 related issue. The current release package is 32 bit, but works (mostly?) when you force the install on a 64 bit system.
I've been doing some work on a new 32 package that uses the Squeak from the Ubuntu repositories. But unfortunately the 64 bit version of the Squeak VM has got some problems....
Offline
Found the answer! just open terminal and run
sudo scratch
Then you can edit it and successfully save
, so it seems like normal permission thing.
EDIT: probably the fact Mcsugarface was able to edit source code is because he saved it in the Desktop or something like that
and my 70th post
Last edited by roijac (2011-08-09 10:26:06)
Offline