Hi Norbert,
I don't think it is RFB's fault either. I did give the complete steps I did.
Perhaps just a wait loop after each of the steps is all it takes, 'cos since I
did those steps using the local vm by hand before the "save and quit". I know
how to wait for RFBServer to start (1), but I'm n
Hi Ben,
Thanks for the welcome :)
My problem doesn't seem to be related to the semaphore issue and more
likely reflects my noob status. I'm up and running now though. I was
afraid of having to run xpra or something since it would eat server
memory, but thankfully RFBServer seems to work fine now.
Hi Srikumar,
can you tell what other software you have installed in your image. I know the
effect but I’m still not fully convinced it is RFBs fault.
Norbert
Am 25.10.2013 um 05:24 schrieb Srikumar Karaikudi Subramanian
:
> Hi,
>
> Since this is my first post, I'd first like to say Pharo roc
Hi Srikumar,
Welcome to the community. Really great to hear you are enjoying Pharo,
and got your problem solved yourself. Hope to see more of you here.
I don't have a direct answer for your queries. I haven't used RFB like
that before. I remember a thread about RFB and semaphores that migh
Yes, because when you openInWorld, you do not create a window,
you take Pharo window as container :)
Ben
On 25 Oct 2013, at 14:55, b...@openinworld.com wrote:
> Benjamin wrote:
>>
>> eh
>>
>> Basically what is done when you open a spec as world is that the background
>> color changed,
>>
Benjamin wrote:
eh
Basically what is done when you open a spec as world is that the background color changed,
all the morph are closed, and the spec is specified to take all the space.
So to revert it, I think you *only* need to close the spec morph,
set the background color to white,
On 25 oct. 2013, at 13:34, Norbert Hartl wrote:
> I’m thinking about what would be the proper/least annoying way of having
> multiple exception sections. If I have a code block that can emit two
> different exceptions is the only way doing it
>
> [ [ ... ]
> on: Exception1
> do: [ … ] ]
>
On 25 October 2013 13:34, Norbert Hartl wrote:
> I’m thinking about what would be the proper/least annoying way of having
> multiple exception sections. If I have a code block that can emit two
> different exceptions is the only way doing it
>
> [ [ ... ]
> on: Exception1
> do: [ … ] ]
>
I’m thinking about what would be the proper/least annoying way of having
multiple exception sections. If I have a code block that can emit two different
exceptions is the only way doing it
[ [ ... ]
on: Exception1
do: [ … ] ]
on: Exception2
do: [ … ]
on:do: just calls a primitive th
On 25 Oct 2013, at 11:34, Manfred Kröhnert wrote:
> Hi,
>
> I tested it it without hurrying today.
> Using Cmd+s with 'whenTextIsAccepted:' works both on Pharo 2.0 and 3.0.
> Unfortunately I exchanged the TextModel with TextInputFieldModel where it did
> not work.
>
> However, using 'whenTextC
Hi,
I tested it it without hurrying today.
Using Cmd+s with 'whenTextIsAccepted:' works both on Pharo 2.0 and 3.0.
Unfortunately I exchanged the TextModel with TextInputFieldModel where it
did not work.
However, using 'whenTextChanged:' does not work or at least not how I
expect it to work.
>From
Hi list,
After successfully installing the Arduino package, I noticed this Getting
Started text:
*After installing the Arduino packages by evaluating...*
*
*
* ConfigurationOfArduino load.*
* *
*...you'll need a couple extra support files in order to be able to upload
programs to your Arduino boa
I have problem to add people : Torsten and you to pharoextras
I mentioned it to Nicolas.
He is looking at it.
Stef
On Oct 24, 2013, at 6:26 PM, Paul DeBruicker wrote:
> Hi Stef,
>
> Will you please add me to the PharoExtras/JSON repo?
>
>
> Thanks
>
> Paul
>
>
>
> On Oct 23, 2013, at 2:
13 matches
Mail list logo