Actually if I just execute before saving on Windows the following code I
get no error when opening the image on Mac:
OmSessionStore allInstancesDo: [ :each |
SystemAnnouncer uniqueInstance unsubscribe: each ].
On Thu, Apr 27, 2017 at 9:48 PM, Andrei Chis
wrote:
> Loaded slice 19990 and the is
Loaded slice 19990 and the issues is still there with the latest image+vm.
On Thu, Apr 27, 2017 at 9:07 PM, Denis Kudriashov
wrote:
> Hi.
>
> 2017-04-26 15:06 GMT+02:00 Andrei Chis :
>
>>
>> I saw that there are a few issues about images saved on an operating
>> system not working when opened on
Hi.
2017-04-26 15:06 GMT+02:00 Andrei Chis :
>
> I saw that there are a few issues about images saved on an operating
> system not working when opened on other operating systems:
> - https://pharo.fogbugz.com/f/cases/19852/Unable-to-open-
> image-in-OSX-after-it-has-been-updated-in-Windows
> - ht
Hi Martin,
On Thu, Apr 27, 2017 at 6:14 AM, Martin Dias wrote:
> Hi Andrei,
>
> Could you tell me what's your "EpMonitor current sessionStore baseLocator"
> ?
>
It's 'a FileLocator {localDirectory}\ombu-sessions'
>
> By default it's a FileLocator, but maybe you personalized it and setted a
>
Hi Andrei,
Could you tell me what's your "EpMonitor current sessionStore baseLocator" ?
By default it's a FileLocator, but maybe you personalized it and setted a
FileReference. FileLocators don't have a WindowsStore but FileReference do.
The OmSessionStore is part of Epicea, and has a startUp: t
What about loading some TTF fonts into the image?
--Hannes
On 4/26/17, p...@highoctane.be wrote:
> I'd say that one should clear all fonts being loaded, refresh the list of
> available fonts because they are on another location (and this should
> happen even moving from windows to windows), and
I'd say that one should clear all fonts being loaded, refresh the list of
available fonts because they are on another location (and this should
happen even moving from windows to windows), and switch back to a default
font that is sure to be available.
I got an issue with the "hack" font because t
Any hints about how to handle Freetype fonts?
Right now I'm getting also some segmentation faults when opening on mac an
image saved on windows, that seem related to Freetype fonts.
On Wed, Apr 26, 2017 at 5:04 PM, p...@highoctane.be
wrote:
> You will also face serious fun with Freetype fonts.
>
You will also face serious fun with Freetype fonts.
Phil
On Wed, Apr 26, 2017 at 3:06 PM, Andrei Chis
wrote:
> Hi all,
>
> I saw that there are a few issues about images saved on an operating
> system not working when opened on other operating systems:
> - https://pharo.fogbugz.com/f/cases/1985
Yesterday I had exactly the same problem. Worked with an image in Windows
during the morning and in the evening tried to open it on my mac with no
success.
The error I had was indeed a path problem. The image was trying to resolve a
path in windows.
I eventually got the image running but with limit
Hi all,
I saw that there are a few issues about images saved on an operating system
not working when opened on other operating systems:
-
https://pharo.fogbugz.com/f/cases/19852/Unable-to-open-image-in-OSX-after-it-has-been-updated-in-Windows
-
https://pharo.fogbugz.com/f/cases/19869/Infinite-loop
11 matches
Mail list logo
