Le 7/4/15 15:19, Thierry Goubier a écrit :
Le 07/04/2015 15:14, Tudor Girba a écrit :
This setting should be removed. Does anyone have anything against that?
Or, could settings be rewritten so that we don't regularly triggers
DNUs and MNUs when we reload them?
You know, just regular, declarative, boring settings instead of
something which execute code on non-existent Classes half of the time...
We started to extract tge configuration code out of pillar but we do not
know if it will work for settings.
So far no time to check.
It is called cocoon on pharoextras
Stef
Thierry
Doru
On Tue, Apr 7, 2015 at 2:45 PM, Esteban Lorenzano <[email protected]
<mailto:[email protected]>> wrote:
that’s not FFI, is NBOpenGL :)
> On 07 Apr 2015, at 14:35, Richard Wettel <[email protected]
<mailto:[email protected]>> wrote:
>
> Hi
>
> I bumped into a broken setting in FFI (see attached Screenshot).
> After I exported the settings, every time I open an image a DNU
comes to greet me:
>
> NBGlxAPI class>>moduleName:
>
> From the implementation, it seems the setting does not make much
sense. Or if it does to somebody, it is probably still missing some
part.
>
> Cheers
> Ricky
>
> <ffiSetting.PNG>
--
www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
