|image|
image := ZnEasy getJpeg:
'http://www.bing.com/th?id=OHR.NubbleLight_EN-US4307721919_1920x1080.jpg&rf=LaDigue_1920x1080.jpg&pid=hp'.
World
backgroundImage: image
layout: #scaled.
On 8/7/19 11:32 AM, Torsten Bergmann wrote:
Dale wrote:
I used the double click trick on "Log file name" and followed it to the above
messages
for the records:
Beside double click you can also right click on a setting and select "Browse"
to find
where it is implemented. You can then also "S
Dale wrote:
>I used the double click trick on "Log file name" and followed it to the above
>messages
for the records:
Beside double click you can also right click on a setting and select "Browse"
to find
where it is implemented. You can then also "Save" the current settings.
The settings frame
I've finally been able to answer my own question. Execute the following
and no more PharoDebug.log and no more stack dump to stdout/stderr (I'm
not exactly sure which debugger is being used, so I set both for good luck):
DebugSession logDebuggerStackToFile: false.
GTGenericStackDebugger
Ciao,
i have a old
Pharo1.4
Latest update: #14445
run on MacBook with Mac OS X 10.7.5 ( Lion ).
In this system the Pharo image run fine.
I copy the relative folder on a MacBook with Mac OS X 10.14.6 (
Mojave ).
No
Hi everyone,
Reminder: the deadline is Sunday August 18.
> Begin forwarded message:
>
> From: "N. Bouraqadi"
> Subject: ESUG Innovation Technology Awards Call for submissions
> Date: 9 July 2019 at 16:08:49 CEST
> To: Board ESUG , Any question about pharo is welcome
>
>
> Dear Smalltalkers,
