Rebuilding Software for BeagleBoard

This appears to affect Obey as well, as I haven’t used any other modes I am unsure if they are meant to have buttons or not! :@)

The thing to check then, is if you have the !Buttons module in the !Zap.Modules directory.
If so, check the module is loaded with *help zapbuttons at a command prompt.
You should get version 2.03 reported.

!Buttons exists in !Zap.Modules

*help zapbuttons
No Help Found

A “me too”. I cannot get Buttons to work in Zap 1.48 tnk-7 on an ARMini.
!Buttons 2.03 is present in Modules but the ZapButtons module never makes it into RMA.

While not making any progress with that issue I did find two 26bit files in MakeMenus.

I note that on the Iyonix though Buttons works the Module does not appear in the Mode menus, it does in the 26bit 1.45 on VRPC. (Take2, it’s not meant to is it, this moved to the Display menu.)

I transferred ZapUser from the Iyonix to the ARMini but Zap stalled on startup complaining about the absence of ZapModules:!Buttons.ZapButtons. I copied the existing Buttons module with the filename ZapButtons and the Buttons did appear.

In the good old day of 26bit-ness the Buttons module had a filename of ‘ZapButtons". These days the filename is ’Buttons’. I rather guess some consequential change has gone wrong??

Hmm, I did as you did David, but still no option / button pane in Zap

It is fair to say that my !ZapUser from the Iyonix may have been around the houses a bit. Anyway I now have Buttons working on the ARMini without having to fiddle around with the Buttons module’s filename. I uploaded my !ZapUser to http://pittdj.co.uk/temp/zbuttons.zip as a temporary measure.

Click Menu on !Zap’s icon bar icon, click Options > Display and Buttons should appear greyed out at the bottom of the Display sub-menu. Create a new BASIC file are there are the Buttons.

Thanks David!

That did the trick, I hadn’t realised how much I used the buttons until they were gone… How cliché is that?

I’d really appreciate it if we were able to get to a “proper” explanation of why this isn’t working (ie. without having to duplicate someone else’s config files), as I’d like the version we have on the ARMini (and the main distribution, for that matter) to work nicely “out of the box”.

Is this really just a problem with the filenaming of Buttons vs ZapButtons, or is there more to it?

The filename thing as it turns out was red herring, that !ZapUser from my Iyonix was not entirely vanilla.

By a process of substitution, rather than actual understanding, the stoppage in the current !ZapUser is due to missing ZapButtons entries in !ZapUser.Config.Menus.UK and !ZapUser.Config.Menus.Source.UK. Without a Button entry anywhere the Buttons cannot be enabled.

I will zip something to RComp for the ARMini.

Many thanks :)

Well spotted David.
The archive on my website did contain the !ZapUser from the 1.45 distribution, which as David found does not have the correct menu structure.
I have now updated it to the one from the 1.47 distribution, so anyone else downloading from scratch should be OK.

anyone else downloading from scratch should be OK.

Not sure if this is the best place to report, as no email in download, but I’m afraid I’m still having problems. (RISC OS 5 on RPCemu.)

Help ZapButtons gives a positive now, however:

• Shift-double-clicking an Obey file or trying to load Obey mode gives “SWI &1DEF02 not known”.

• Adjust click to open new BASIC file gives Address Exception.

Just an idea: disabling Buttons may solve this issue, but I’m unsure of how to do this. Also, many thanks to Tank for continuing to develop Zap as I find it infinitely preferable to StrongEd or (Src)Edit.

@hilltop I am seeing the same on OS5.17 on rpcemu 0.8.8 on a Mac with Zap 1.48 and 1.47. 1.47 is OK on the Iyonix and 1.48 is OK on the ARMini. (The rpcemu 5.17 ROM is dUI300-00 which I believe is a Tom Walker special.)

A trifle, !ZapFonts in the full download is a bit empty, it only has the module in it.

I am seeing the same on OS5.17 on rpcemu 0.8.8

Hmm, looks like a Dynarec issue since following your post I tested with the interpreted version and all worked as expected.

I’ll report this to the RPCEmu list. Thanks for the confirmation it’s not just me seeing this.

Just an idea: disabling Buttons may solve this issue, but I’m unsure of how to do this. Also, many thanks to Tank for continuing to develop Zap as I find it infinitely preferable to StrongEd or (Src)Edit.

I think calling it development may be a little overstated…
I’m really just tinkering with it.

A trifle, !ZapFonts in the full download is a bit empty, it only has the module in it.

I did mention on the download page that you need to get a full copy of !ZapFonts, as it is quite a big archive on its own.

I have now updated the download to include the full !ZapFonts.

Well, thanks for tinkering then, it is most appreciated.

I’m crossing this info over from the Rattling scroll bars thread, so as not to hijack that one. This seems more appropriate for BB !Zap issues.

Has anyone else seen redraw problems like this (on the BB xM, Zap 1.48, ZapRedraw 0.48 (07 Apr 2010)):

This shows the result of horizontal scroll. Vertical scrolling does the same on the other two boundaries.

Tried repeating with all the colour resolutions from 16M down to black & white. Same effect.

I have used Zap 1.48 on the ARMini a lot, and never seen the effect you are describing. I always use 16M colour at 1920×1080.

My monitor’s limited to 1024×768.

Stopped testing lower resolutions after killing my boot disc. Went into an unsupported resolution and, being rusty on ROS stuff, forgot that [CTRL][SHIFT][F12] was my friend. Yup, I do make backups.

WPB suggested that a bug in ZapRedraw’s VDU anti-aliased font display might be responsible for the redraw errors. I changed to DSA at his suggestion and the problem’s gone.

Continuing with Zap, in a recent disc build there’s a text(?) file !Boot.Library./cvstag. Opening with Zap generates the error ‘Module ’ZapInform is not 32 bit compatible’’.

Continuing with Zap, in a recent disc build there’s a text(?) file !Boot.Library./cvstag. Opening with Zap generates the error ‘Module ’ZapInform is not 32 bit compatible’’.

Not entirely persuaded that the ZapInform module should be hoovering up that filename but it certainly does.

&500 &FFF \#\*.library.\o\* +Inform

The module, 1.0b 24 Sep 1997, is indeed 26bit but Inform itself, an adventure game compiler, is somewhat obsolete, at least I have never heard of it, so !ZapInform could be dispensed with.

Inform […] never heard of it

It’s an interactive fiction language developed by Graham Nelson, after he wrote Curses on the Archimedes.

It’s an interactive fiction language developed by Graham Nelson, after he wrote Curses on the Archimedes.

It turns out to be not quite as obsolete as first thought, Inform 6.30, 32bit