[squeak-dev] Scratch 1.4 on squeak-vm 4.10

David T. Lewis lewis at mail.msen.com
Sat Mar 15 17:15:58 UTC 2014


There are two VM command line options that relate to Sugar ("squeak -help"
to see these):

  -sugarBundleId <id>   set window property _SUGAR_BUNDLE_ID to <id>
  -sugarActivityId <id> set window property _SUGAR_ACTIVITY_ID to <id>

I am not really sure what these do, but they relate to the image interacting
with X windows, so you might want to check and see if there is some difference
in the way that you open Scratch on Sugar, compared to the way that you
open Scratch without Sugar.

Dave

On Fri, Mar 14, 2014 at 09:57:03AM -0300, Gustavo Duarte wrote:
> No, the only application with this problem is Scratch, moreover, Scratch 
> running on Sugar in the same machine work fine.
> 
> Thanks in advance.
> 
> Gustavo.
> 
> 
> On 03/13/2014 09:07 PM, gettimothy wrote:
> >Do other fullscreen applications trigger the problem?
> >
> >tty
> >
> >
> >
> >---- On Thu, 13 Mar 2014 15:49:28 -0700 *tim 
> >Rowledge<tim at rowledge.org>* wrote ----
> >
> >
> >    On 13-03-2014, at 3:37 PM, Gustavo Duarte <gus.duarte at gmail.com
> >    <mailto:gus.duarte at gmail.com>> wrote:
> >    > You are gave me an awesome tip.
> >    >
> >    > I loaded a Squeak3.9a.from3.0.image, and tried "full screen on"
> >    and "full screen off" from Menu, and after "full screen off" same
> >    error happened. The screen turned up white and nothing else i
> >    could did. As i started from terminal, i finished the application
> >    with ctrl+C.
> >    >
> >    > With this test, could we say that the issue is inside squeak-vm
> >    code ?
> >    >
> >    > Other suggestion to follow finding out where is this bug ?
> >
> >    I'd say that strongly suggests a problem in the code setting the
> >    screen mode; you'll find it (for unix) in
> >    platforms/unix/vm-display-X11/sqUnixX11.c at the function
> >    display_ioSetFullScreen(sqInt fullScreen). Since it works on many
> >    unices and has for a long time I imagine it means some problem
> >    with the specific machine's display driver code. That could be all
> >    sorts of fun to solve. At the very least you'll need to find an X
> >    expert, which is not me.
> >
> >
> >    tim
> >    -- 
> >    tim Rowledge; tim at rowledge.org <mailto:tim at rowledge.org>;
> >    http://www.rowledge.org/tim
> >    BASIC is to computer programming as QWERTY is to typing.



More information about the Squeak-dev mailing list