Groups | Search | Server Info | Login | Register
Groups > comp.sys.acorn.misc > #21799
| From | Dave <dave@triffid.co.uk> |
|---|---|
| Newsgroups | comp.sys.acorn.misc |
| Subject | Re: RO Pinboard problem |
| Date | 2026-02-06 20:29 +0000 |
| Organization | TLP |
| Message-ID | <5ca71058a5dave@triffid.co.uk> (permalink) |
| References | <5ca661bd9adave@triffid.co.uk> <5ca6750cf6dave@triffid.co.uk> <353003a75c.Paul@phorefaux> |
In article <353003a75c.Paul@phorefaux>, Paul Stewart <phorefaux@gmail.com> wrote: > In message <5ca6750cf6dave@triffid.co.uk> > Dave <dave@triffid.co.uk> wrote: > > In article <5ca661bd9adave@triffid.co.uk>, > > Dave <dave@triffid.co.uk> wrote: > >> VRPC-DL RISC OS 6.20 > >> I have a Pinboard problem and wondered what's going on. > >> I have a file called "BP2602" and a reference to it in the Pinboard > >> Tasks.Obey file. [Snip] > Okay. I have fired up my VRPC running 6.20 and I can replicate your > issue. I cannot replicated on my A9home running 4.42 due to not having > the same options. > Issue on RO6 would appear to be due to the "Object name display" setting > from within Configure-Pinboard-Interface. Under "Object name display" > there a setting: "Show all CAPS in lower case". When ticked this shows > the non numeric portion of the filename that are all in capitals as > lower case: - > BP2602 = bp2602 > BPx2602 = BPx2602 (this displays correctly because the non > numeric part of the filename is is mixture of cases and not all > uppercase > BP6202z = BP6202z (works for same reason as above) > Hope this helps :) Paul, Give that Man a score of Eleven out of Ten. An absolutely wonderful catch. That was indeed the problem, now fixed. Much appreciated, thanks Dave Nb: Interestingly, many previous experiments showed it was a RISC OS 6.20 problem, and that it didn't happen on any RISC OS 4.39 installs I tested. Nor even a RPCEmu and RISC OS 5.31. Neither RISC OS 4.39 or RISC OS 5.3nn have that Pinboard configure option. D. -- Dave Triffid
Back to comp.sys.acorn.misc | Previous | Next — Previous in thread | Next in thread | Find similar
RO Pinboard problem Dave <dave@triffid.co.uk> - 2026-02-05 12:42 +0000
RO Pinboard problem Dave <dave@triffid.co.uk> - 2026-02-05 16:13 +0000
Re: RO Pinboard problem Paul Stewart <phorefaux@gmail.com> - 2026-02-06 18:05 +0000
Re: RO Pinboard problem Dave <dave@triffid.co.uk> - 2026-02-06 20:29 +0000
Re: RO Pinboard problem druck <news@druck.org.uk> - 2026-02-07 11:40 +0000
Re: RO Pinboard problem Paul Stewart <phorefaux@gmail.com> - 2026-02-07 12:01 +0000
Re: RO Pinboard problem Dave <dave@triffid.co.uk> - 2026-02-07 15:54 +0000
Re: RO Pinboard problem druck <news@druck.org.uk> - 2026-02-11 00:34 +0000
Re: RO Pinboard problem Dave <dave@triffid.co.uk> - 2026-02-11 09:11 +0000
Re: RO Pinboard problem Martin <News04@avisoft.f9.co.uk> - 2026-02-11 09:38 +0000
Re: RO Pinboard problem Dave <dave@triffid.co.uk> - 2026-02-12 09:12 +0000
Re: RO Pinboard problem Paul Stewart <phorefaux@gmail.com> - 2026-02-13 18:31 +0000
Re: RO Pinboard problem druck <news@druck.org.uk> - 2026-02-11 21:21 +0000
Re: RO Pinboard problem Chris Hughes <news13@noonehere.co.uk> - 2026-02-11 21:43 +0000
Re: RO Pinboard problem Paul Stewart <phorefaux@gmail.com> - 2026-02-13 18:21 +0000
Re: RO Pinboard problem Jean-Michel <jmc.bruck@orange.fr> - 2026-02-06 10:11 +0100
Re: RO Pinboard problem Richard Ashbery <basura@invalid.addr.uk> - 2026-02-06 12:15 +0000
Re: RO Pinboard problem Chris Hughes <news13@noonehere.co.uk> - 2026-02-06 13:10 +0000
Re: RO Pinboard problem Richard Ashbery <basura@invalid.addr.uk> - 2026-02-06 15:09 +0000
csiph-web