ð Syntax10.Scn.Fntîÿÿÿð¹õ ¿ParcElemsAlloc ÆêÀ²°š ÐíSyntax10b.Scn.Fnt%;Syntax10i.Scn.Fnt ÖI %€yó[†To all users of Dialogs on MacOberon: Oberon Dialogs should run under nearly all (Oberon V4) platforms (including a working Oberon-2 compiler) without and changes to the system and to Oberon Dialogs. Nearly all means not all: MacOberon is the exception. You have to do some changes in the Dialogs system. 1st: When you fetch MacOberon fetch also Compiler2 and Display1 (should be part of the Kepler distribution of MacOberon). 2nd: Because the standard distribution of MacOberon is the only distribution without an Oberon-2 compiler you may not use Folds: You have have to use the Compiler2.Compile command. The only file which includes fold elements is MyUI.Mod. Make a FoldElems.Expand and after that an Edit.Store. 3rd: The definition of the module Types in MacOberon is different to other platforms. On PowerMac, Windows, Sparc, RS6000 a.s.o. the following definition is used: Types.TypeDesc = RECORD name: ARRAY 32 OF CHAR; module: Modules.Module END; On the other side, MacOberon uses following definiton: Types.TypeDesc = RECORD name, module: ARRAY 32 OF CHAR; END; Therefore the following change in the dialog sources is necessary: In Dialogs.Mod and DialogTexts.Mod replace all occurences of 'types.module.name' with 'types.module'. 4th: In MacOberon a Browser.ShowDef of the module Modules is not possible. Therefore I am not sure if there exists a type 'Modules.ModuleName'. Use instead of that type name an 'ARRAY 32 OF CHAR' in module Dialogs.Mod. Additionally replace 'tab1[end1] := type.module.name' with 'COPY (type.name, tab1[end])' I think with this changes Oberon Dialogs should run even under MacOberon. ;-)