Branch: refs/heads/6.0
Home: https://github.com/pharo-project/pharo-core
Commit: e20540de9c14cddb2c88d186e14aa6ce3db782bc
https://github.com/pharo-project/pharo-core/commit/e20540de9c14cddb2c88d186e14aa6ce3db782bc
Author: Jenkins Build Server
Date: 2016-07-04 (Mon, 04 Jul 2016
Branch: refs/tags/60133
Home: https://github.com/pharo-project/pharo-core
I tried to see if it was the name usage but this is a problem I do not
get :)
When I interrupted the program it was
open: fileName forWrite: writeMode
"Open the file with the given name. If writeMode is true, allow
writing, otherwise open the file in read-only mode."
| f |
f := fi
Hi doru
I'm not sure that you know that ConfigurationOfAthens-TudorGirba.87 does
not load in latest 60
It seems a problem with Object>>name usage (deprecation leading to an
problem).
In Pharo 60 we have MarcusDenker.82 and the latest stable in the repo is
ConifgurationOfAthens-TudorGirba.8
Hi Jeff,
if you use forms to paint on an AthensCairoCanvas, they are cached in the
CairoBackendCache,
can you try to flush that cache whith
CairoBackendCache flush.
2016-06-18 18:36 GMT+02:00 J.F. Rick :
> I'm using Athens rendering for my multi-touch applications on Pharo5. As
> part of that,
I just noticed it seems class variables are not shown in Variables
pane of GTDebugger. It confused me for a while, and I expect it would
be troubling for newcomers. Is this due to copying the previous
Debugger functionality here, or some other design decision?Any
reason to not display class v
On Sun, Jul 3, 2016 at 7:25 PM, Bernhard Pieber wrote:
> Done!
Thanks Bernhard, but I can't find the issue in the tracker. Can you
paste a link?
On Sun, Jul 3, 2016 at 7:41 PM, Bernhard Pieber wrote:
> I wonder about the process for fixes for Pharo 4.0? Is it the same? If I’d
> put the equiva
Thank you.
> On 03 Jul 2016, at 13:25, Bernhard Pieber wrote:
>
> Done!
>
> Cheers,
> Bernhard
>
>> Am 03.07.2016 um 00:08 schrieb Ben Coman :
>>
>> On Sun, Jul 3, 2016 at 3:16 AM, Bernhard Pieber wrote:
>>> Hi,
>>>
>>> The following code goes into an endless loop:
>>> MailAddressParser add
I wonder about the process for fixes for Pharo 4.0? Is it the same? If I’d put
the equivalent fix into the Pharo40Inbox, would it be integrated?
Cheers,
Bernhard
> Am 03.07.2016 um 08:46 schrieb stepharo :
>
> Thanks Bernhard
>
> - can you open a bug entry?
>
> - publish a slice? (press slice
Done!
Cheers,
Bernhard
> Am 03.07.2016 um 00:08 schrieb Ben Coman :
>
> On Sun, Jul 3, 2016 at 3:16 AM, Bernhard Pieber wrote:
>> Hi,
>>
>> The following code goes into an endless loop:
>> MailAddressParser addressesIn: 'romeo&ju...@verona.it‘
>>
>> It’s because of the ampersand. The fix is t
On Sun, Jul 3, 2016 at 6:08 AM, Ben Coman wrote:
> On Sun, Jul 3, 2016 at 3:16 AM, Bernhard Pieber wrote:
>> Hi,
>>
>> The following code goes into an endless loop:
>> MailAddressParser addressesIn: 'romeo&ju...@verona.it‘
>>
>> It’s because of the ampersand. The fix is trivial, because the bug j
11 matches
Mail list logo