Thank you Esteban! I've downloaded the latest VM and fonts on cairo now work. I believe this was the last VM crash I am aware of, so hopefully I will have a productive and stable year with Pharo 6. :)
(I had some issues with dlls not loading on startup sometimes (mentioned in other thread SurfacePlugin.dll)... but this correlates with some other Windows issues...so I need more info myself). Thanks! Peter On Mon, Apr 03, 2017 at 12:12:08PM +0200, Esteban Lorenzano wrote: > Hi Peter, > > I think I fixed the problem, can you try latest vm? > > Esteban > > > > On 31 Mar 2017, at 14:55, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > > > > Peter I took the latest mac VM and Moose 6.1 and I used your example > > then I played during 15 min with all the roassal examples and I cannot > > reproduce > > but I'm on mac. > > > > > > > > On Fri, Mar 31, 2017 at 2:23 PM, Stephane Ducasse <stepharo.s...@gmail.com > > <mailto:stepharo.s...@gmail.com>> wrote: > > Tx peter! > > I really really sorry for this state of affair. > > I would like to tell you that I thank you for all the feedback you sent. > > Please continue. > > I imagine what it is to get a system that blow up under your fingers. > > I'm always trying to work with the alpha version (because I attract bugs) > > I got some crashes playing with roassal - but I updated to the latest vm > > and trying. > > > > Can you sync with esteban so that he can access your setup? And yes we are > > burning > > esteban on this.... We should pay attention that our faery does not get too > > exhausted :). > > > > Stef > > > > > > On Fri, Mar 31, 2017 at 1:10 PM, Peter Uhnák <i.uh...@gmail.com > > <mailto:i.uh...@gmail.com>> wrote: > > > > > > On Wed, Mar 29, 2017 at 3:03 PM, Esteban Lorenzano <esteba...@gmail.com > > <mailto:esteba...@gmail.com>> wrote: > > BTW… I just checked Latest VM with a Pharo 5.0 (50771), and FT2 DOES NOT > > CRASHES… and it looks working fine, just installed somethings, etc. so I > > cannot be sure it will remain like that, but I can tell you: FT2 fonts are > > working fine in Windows (tested in 7) and Pharo 5.0 *with* latest VM. > > > > So, all this discussion is informative, but the mail that originates it can > > be reviewed :) > > > > No, this is still broken, even in Pharo 6 (with the latest VM). Maybe it's > > yet another cairo issue? But it complains about FT fonts... > > > > I did mention that it crashed on Athens canvas, so e.g. any Roassal > > presentation that contains text > > > > v := RTView new. > > v add: (RTLabel new elementOn: '-_-'). > > v > > > > <fml.png> > > > > > > Or running AthensSurfaceExamples class>>exampleDrawText > > > > <fml_squared.png> > > > > > > In the past 15 months there was not a single week when the VM would just > > work without crashing or failing, and seeing that Pharo 6/lastest VM one > > day before release still doesn't work makes me really question why I still > > put up with this. > > > > Peter > > > > > > > > Esteban > > > > > >> On 29 Mar 2017, at 14:43, p...@highoctane.be <mailto:p...@highoctane.be> > >> wrote: > >> > >> We cannot work in 5.0 professionally with the VM released at the time. > >> I am also using an intermediate VM thing to do the job. > >> > >> That is a pain. And not helping me push more Pharo to sysadmin people > >> because they cannot have a stable reference point. > >> > >> Phil > >> > >> On Wed, Mar 29, 2017 at 12:05 PM, Esteban Lorenzano <esteba...@gmail.com > >> <mailto:esteba...@gmail.com>> wrote: > >> > >> > On 29 Mar 2017, at 11:39, Peter Uhnak <i.uh...@gmail.com > >> > <mailto:i.uh...@gmail.com>> wrote: > >> > > >> > On Wed, Mar 29, 2017 at 11:05:28AM +0200, Esteban Lorenzano wrote: > >> >> well… > >> >> > >> >> Latest VM is intended to work with latest Pharo, not with older > >> >> versions. > >> >> Latest VM is *always* an experimental/unstable VM that needs to be > >> >> considered… that, experimental and unstable. Otherwise there would not > >> >> be point on having the distinction between stable/latest, isn’t? > >> >> > >> > > >> >> So, no, Latest VM (which can also be known as “alpha vm”) has not > >> >> broken FT, it works fine in Pharo 6.0, which can also be know as “Pharo > >> >> 6.0 Alpha”). > >> >> > >> >> BTW… That’s why in zeroconf you cannot download a “latest vm for Pharo > >> >> 5”. > >> >> > >> >> Of course, you can live at the edge, but that doesn’t means something > >> >> is broken when something fails if premises are not fulfilled :) > >> > > >> > Well considering VM for Pharo 5 never worked for me properly, whether it > >> > was crashing on BitBlt/Cairo, FT, or who knows what, I don't really have > >> > a choice but to use the latest. If there is a better way then I am all > >> > ears, constantly dealing with crashing VM when I need to get work done > >> > is extremely frustrating... > >> > > >> > Also I was under the impression that newer VM should work with older > >> > images, with the only exception being Cog/Spur change. Or should I have > >> > six different VMs and Pharo Launcher with six different VM > >> > configurations? > >> > >> we moved the paradigm a couple of years ago: each Pharo version comes with > >> his own VM version (Other smalltalks do that too). > >> Being infinite backward compatible is a lot of pain :) > >> > >> so yes, PharoLauncher needs to adapt to it… I added that requirement for > >> PharoLauncher: you ship with latest stable but you can always download > >> newers or olders (this is not yet implemented, is just a requirement I > >> added… well, couple of years ago when we changed the way we wanted VMs to > >> work). > >> > >> Esteban > >> > >> > > >> > Peter > >> > > >> >> > >> >> Said that… I had no problems with Latest VM + Pharo 6.0 (and they may > >> >> happen, since this is all alfa :P) > >> >> > >> >> I don’t know if “workarounding the VM” (by renaming libfreetype) will > >> >> work, but if that works, ONCE we move latest vm to stable status we can > >> >> consider backporting it to Pharo 5. > >> >> > >> >> Esteban > >> >> > >> >>> On 29 Mar 2017, at 10:37, Peter Uhnak <i.uh...@gmail.com > >> >>> <mailto:i.uh...@gmail.com>> wrote: > >> >>> > >> >>> The new "fixed" compactor VM has broken FT... > >> >>> > >> >>> So any text drawn on Athens canvas results in red cross... > >> >>> > >> >>> Error in... > >> >>> > >> >>> CairoFontFace class>>primFtFace:loadFlags: > >> >>> > >> >>> 'Unable to find function address' > >> >>> > >> >>> Apparently because someone renamed libfreetype-6.dll to libfreetype.dll > >> >>> > >> >>> (Windows VM latest, Pharo 5) > >> >>> > >> >> > >> >> > >> > > >> > >> > >> > > > > > > > > >
