I was doing the following in one of my projects...
Set SomePath$Path <Obey$Dir>.SomeDir.
Filer_OpenDir SomePath:
On v4.02, this, in an Obey file does exactly what you'd expect in that
it opens a window showing the contents of SomeDir. On v4.39 (1i2) the
same obey file will just chuck up an "Unrecognised FileName" error...
The obvious work-around for this is to setup <SomePath$Dir> to the
same value, but without the trailing dot and Filer_OpenDir that. I'm
just surprised that someone hasn't spotted and fixed this one already.
Or am I taking shortcuts that I shouldn't be taking?
Thanks for any advice...
> I was doing the following in one of my projects...
> Set SomePath$Path <Obey$Dir>.SomeDir.
> Filer_OpenDir SomePath:
> On v4.02, this, in an Obey file does exactly what you'd expect in that
> it opens a window showing the contents of SomeDir. On v4.39 (1i2) the
> same obey file will just chuck up an "Unrecognised FileName" error...
> The obvious work-around for this is to setup <SomePath$Dir> to the
> same value, but without the trailing dot and Filer_OpenDir that. I'm
> just surprised that someone hasn't spotted and fixed this one already.
It has been spotted, many years ago. There was a thread about it called
'Pseudo filing systems: filer still unable to access root directory' on
the Select mailing list in May/June 2002 and another one called 'Path
variables ...' in November 2002 [1].
> Or am I taking shortcuts that I shouldn't be taking?
The original behaviour was considered a bug.
Regards,
Frank
[1] This was on Smartgroups at the time. I have no idea whether that was
archived anywhere, so I have put these two threads in a zip at
http://www.aconet.nl/tmp/selml.zip in case you want more info about
this.
The original behaviour was considered a bug by couple of people for weak
reasons and arbitrarily changed so that it breaks stuff for people that
always used to work. This is a good example of how _not_ to develop an OS.
Just like breaking transient all utilities for no good reason.
Steve
--
Steve Revill @ Home
Note: All opinions expressed herein are my own.
OK... Obviously been spotted then. I guess the next question is
whether anyone has submitted a patch to the module or whatever deals
with this and where to get it?
> Just upgraded to v4.39... All OK, but I've spotted something that no
> longer works that used to work with v4.02...
>
> I was doing the following in one of my projects...
>
> Set SomePath$Path <Obey$Dir>.SomeDir. Filer_OpenDir SomePath:
>
> On v4.02, this, in an Obey file does exactly what you'd expect in that it
> opens a window showing the contents of SomeDir. On v4.39 (1i2) the same
> obey file will just chuck up an "Unrecognised FileName" error...
This is a known feature of Select (at least early versions, I'm no longer a
subscriber, so I don't know if it was fixed). There was an argument that it
was a deliberate change, IIRC.
It actually makes some sense: consider
Set SomePath$Path <Obey$Dir>.SomeDir.,Boot:^.AnotherDir.
Now what does *Filer_OpenDir SomePath: open?
> The obvious work-around for this is to setup <SomePath$Dir> to the same
> value, but without the trailing dot and Filer_OpenDir that. I'm just
> surprised that someone hasn't spotted and fixed this one already. Or am I
> taking shortcuts that I shouldn't be taking?
Using <SomePath$Dir> is the better option in most cases; if you really need
to open a path, you probably want to parse it and sort out which folder you
really want to open.
--
Steve Fryatt - Leeds, England
You've got a few choices there:
1. the traditional answer: throw an error - that's what happens
2. open both folders as separate windows - could be handy!
3. open the first - a bodgy answer
4. do nothing at all - yuck
> Using <SomePath$Dir> is the better option in most cases; if you really need
> to open a path, you probably want to parse it and sort out which folder you
> really want to open.
The reason why people liked using a single entry path, which they own and
they _know_ will only ever have one entry on it, is because it doesn't get
canonicalised by the Filer before opening the filer window.
This can result in a nice, tidy "Waste:" window opening, rather than
"ADFS::MyDisc.$.Apps.Miscellaneous.!Wastebasket.TmpDir.Waste".
I think most people would agree that for certain things, it's nice to be
able to present a simplified directory name in the filer window to the user.
Ta,
> On Oct 6, 9:08�am, "Ste (news)" <st...@revi11.plus.com> wrote:
>> In article <50a5d8900czuiderd...@hotmail.com>,
>> � �Frank de Bruijn <zuiderd...@hotmail.com> wrote:
>>
>>> In article <adf2a2c5-ffb7-4c10-b548-7bc2367bb...@d23g2000vbm.googlegro
>>> ups.com>,
>>> � �Gazza <use...@garethlock.com> wrote:
>>>> Or am I taking shortcuts that I shouldn't be taking?
>>
>>> The original behaviour was considered a bug.
>>
>> The original behaviour was considered a bug by couple of people for weak
>> reasons and arbitrarily changed so that it breaks stuff for people that
>> always used to work. This is a good example of how _not_ to develop an OS.
>> Just like breaking transient all utilities for no good reason.
>
> OK... Obviously been spotted then. I guess the next question is
> whether anyone has submitted a patch to the module or whatever deals
> with this and where to get it?
RISC OS 4.39 is a closed source operating system, so it is highly
unlikely that anyone is able to submit a patch for any of its
components. Your only chance is to complain to ROL and ask them to fix
this issue. Supposing they agreed with you and they fixed it in a
future release, you would then still have to buy it.
Martin
--
---------------------------------------------------------------------
Martin Wuerthner MW Software http://www.mw-software.com/
ArtWorks 2 -- Designing stunning graphics has never been easier
spam...@mw-software.com [replace "spamtrap" by "info" to reply]
> In article <mpro.kr3e8u3w...@stevefryatt.org.uk>,
> Steve Fryatt <ne...@stevefryatt.org.uk> wrote:
> > It actually makes some sense: consider
> >
> > Set SomePath$Path <Obey$Dir>.SomeDir.,Boot:^.AnotherDir.
> >
> > Now what does *Filer_OpenDir SomePath: open?
>
> You've got a few choices there:
>
> 1. the traditional answer: throw an error - that's what happens
> 2. open both folders as separate windows - could be handy!
> 3. open the first - a bodgy answer
> 4. do nothing at all - yuck
>
As a matter of fact, I did recently write a BASIC utility to perform
just such a function - recursively canonicalise the pathname (until
there were no more system variables in it) and optionally open either
the first entry or all of them at once. Another neat feature is that if
you passed the argument SomePath:SomeDir.SomeFile, and SomePath$Path had
multiple entries, it would ignore any entries which did not contain
directory SomeDir with SomeFile inside.
Odd things would happen if you tried to open a multiple path which
referred to a second multiple path, but I'm not sure in which
circumstances that would happen anyway.
At the time my big brother asserted nobody would ever want to use it! I
could still make it available, if there's demand...
--
__<^>__ "Your pet, our passion." - Purina
/ _ _ \ "Your potential, our passion." - Microsoft, a few months later
( ( |_| ) )
\_> <_/ ======================= Martin Bazley ==========================
One classic example is Run$Path (especially if you use the build environment
from the RISC OS Open site)... here's my run path right now:
*show run$path Run$Path :
Build:,
Apps:,
ADFS::SRevillX.$.!BOOT.Library.,
ADFS::SRevillX.$.!BOOT.Utils.,
,
%.,
ADFS::SRevillX.$.!BOOT.Resources.!Internet.bin.,
Builds:7thsw.Library.7thsw.,
ADFS::SRevillX.$.Apps.Misc.!Director.Utils.,
Choices:Director.Utils.,
ADFS::SRevillX.$.Work.builds.7thsw.Apps.!Perl.
and to add to the fun:
*show build$path Build$Path(Macro) :
<Tools$Dir>.Acorn.,
<Tools$Dir>.Build.,
<Tools$Dir>.Unix.,
<Tools$Dir>.Misc.,
<Tools$Dir>.,
<Tools$Dir>.DrSmiths.Utilities.,
<Tools$Dir>.7thsw.
So opening Run: would open (I think) 17 filer windows... :)
Something like PathUtils_EnumeratePath
(http://select.riscos.com/prm/programmer/pathutils.html) ?
> and optionally open either
> the first entry or all of them at once.
John.
Someone was obviously lacking in supervision when that was implemented:
"The use of un-specified path components in the use of path variables is thus
discouraged."
Riiiight. And your code will no longer reliably work on anything other than
RISC OS Select. Genius.
"This change ensures that applications which attempt to process paths can do
so in a consistent manner without requiring special cases. Previously it
would have been necessary to check whether a path name terminates in a ':'
character before appending a period and leaf name (that is 'Choices:' cannot
have a regular '.Leaf' appended to it to create a valid filename)."
OK. So to save some tiny fraction of complexity in a simple bit of code that
has already been successfully written a million times, we add a 'feature'
which can and will break other people's perfectly reasonable code (see the
OP's post).
Hmph! If anyone should insist on implementing such a pointless excercise in
breaking backwards compatibilty, at least make it optional with the default
behaviour being "off".
I can't be sure of this, but I think I've since spotted a situation
where this breaks code distributed WITH Select 1i2 in the form of !
Recyclone. Just try selecting the Choices option from the menu on the
icon bar. All I get is a messagebox containing junk! Not satisfied
with breaking other people's code, they're deciding to break their own
too!!!
> I can't be sure of this, but I think I've since spotted a situation
> where this breaks code distributed WITH Select 1i2 in the form of !
> Recyclone. Just try selecting the Choices option from the menu on the
> icon bar. All I get is a messagebox containing junk! Not satisfied
> with breaking other people's code, they're deciding to break their own
> too!!!
If you persist on using a really old version of Select, then you may
as well just stick with vanilla 4.02.
Regards
--
Paul Stewart - Far Bletchley, Milton Keynes, England.
(msn:pauls...@phawfaux.co.uk)
> If you persist on using a really old version of Select, then you may
> as well just stick with vanilla 4.02.
Is that to say that this version of Select was never worth running over
4.02?
B.
TBH not having run that version of Select for so many years, I really
could not say.
Select is a constantly moving target. Running a really old version
and then complaining about possible bugs, is like running Windows 98,
complaining something does not work right and expecting Microsoft to
come along and fix it for you.
OK... Where do I get essential updates without having to subscribe? Or
am I going to have to shell out another load of money to get these
fixes.
> > Select is a constantly moving target.
[Snip]
> OK... Where do I get essential updates without having to subscribe? Or
> am I going to have to shell out another load of money to get these
> fixes.
Yeah!
RISC OS 5 Open Source is the future!
John
--
John Williams, Brittany, Northern France - no attachments to these addresses!
Non-RISC OS posters change user to johnrwilliams or put 'risc' in subject!
Who is John Williams? http://petit.four.free.fr/picindex/author/ Somewhere nice to stay in Brittany? http://petit.four.free.fr/visitors/locate
> On Oct 7, 8:41�pm, Paul Stewart <paulstew...@phawfaux.co.uk> wrote:
[snip]
>>>
>>
>> TBH not having run that version of Select for so many years, I really
>> could not say.
>>
>> Select is a constantly moving target. �Running a really old version
>> and then complaining about possible bugs, is like running Windows 98,
>> complaining something does not work right and expecting Microsoft to
>> come along and fix it for you.
>>
>> Regards
>> --
>> Paul Stewart - �Far Bletchley, Milton Keynes, England.
>> (msn:paulstew...@phawfaux.co.uk)
> OK... Where do I get essential updates without having to subscribe? Or
> am I going to have to shell out another load of money to get these
> fixes.
Well why would you think they should be free.
RISC OS Select gives you 12 months free updates including newer
versions of the OS, it is after all a subscription service.
As Paul has stated this is no different to buying say Windows98 which
had "free" updates for a while and then was depreciated so you can't
get anymore fixes full stop. Worse still any latest OS upgrade is more
than likely to need newer hardware when moving from Windows98 to even
ME,2000 or XP.
What I don't really understand is this "I bought it 12 years ago so I
think I'm right to demand a free upgrade or fix" mentality.
A one off upgrade to RISC OS 6 is just �35.
Or try RISC OS 5 which with out wishing to start a debate on which is
better runs on a RiscPC, just about at the moment, but it does lack
some of the features of Select/ RISC OS 6.
Doug
--
Using an IYONIX pc and RISC OS 5.14, the thinking person's alternative
operating system to Microsoft Windows.
> A one off upgrade to RISC OS 6 is just �35.
>
> Or try RISC OS 5 which with out wishing to start a debate on which is
> better runs on a RiscPC, just about at the moment, but it does lack
> some of the features of Select/ RISC OS 6.
RISC OS 6 clearly runs much better on a RiscPC than RISC OS 5 does -
no debate there*. As for very early versions of Select, and other early
subscribers might remember better than I, but there were indeed
various annoying bugs that sometimes made RO4 a better choice, but
those were quickly resolved. But it's been so long I can't
remember any of the details.
Quite true - we've not finished the RiscPC HAL for one thing so off the top
of my head I can think of a couple of minor bits that won't work in RISC OS
5 on the RiscPC:
* hard drives
* networking
* your CMOS gets reset every boot
* hardware scrolling
* hardware acceleration of moving windows
I'm sure there are other minor niggles, too. ;)
I don't remember exactly the last version number of Select 1,
but I still use it on one of my Risc PCs and it is a big improvement
on vanilla 4.02 - DHCP and Joliet CDFS amongst other major features.
It is also completely stable and the only annoying thing is its
"I won't load your 32bit CLib feature", which is easily patched away.
Multi-User boot also comes handy sometimes.
Indeed I would say that it was probably the biggest step forward in
Select history, at least concerning the user-facing changes. Second was
probably Select 3 with global cut&paste, IFR integration, Filer
thumbnailing and the wastebin.
Not much has happened since then, especially for ViewFinder users.
Steffen
--
Steffen Huber
hubersn Software - http://www.hubersn-software.com/
> > OK... Where do I get essential updates without having to subscribe?
> > Or am I going to have to shell out another load of money to get
> > these fixes.
>
> Well why would you think they should be free.
You paid for Windows 98 once, and got several years of free updates.
> RISC OS Select gives you 12 months free updates including newer
> versions of the OS, it is after all a subscription service.
Hardly "free"; you pay for a 12 months subscription. This is a bit
like saying you give a magazine a bundle of money for 12 months of free
issues!
B.
OK... Brought the Upgrade kit from the RISC OS Ltd stand at the RUGOL
show on the 3rd October... How do I register for the updates if
they're included in the price of the upgrade kit??
> Select is a constantly moving target. Running a really old version
> and then complaining about possible bugs, is like running Windows 98,
> complaining something does not work right and expecting Microsoft to
> come along and fix it for you.
Actually it's more like running a beta release of Win 98.
The only 'final' versions of RO4 are 4.02 (and the OEM 4.0x variants
thereof) and 4.39. All the rest were, as Paul says, a 'moving target' and
although some (such as 4.29) are known to be pretty solid, others may well
have problems which were fixed in later releases.
--
David Holden - APDL - <http://www.apdl.co.uk>
[snip]
>>
>> - Show quoted text -
> OK... Brought the Upgrade kit from the RISC OS Ltd stand at the RUGOL
> show on the 3rd October... How do I register for the updates if
> they're included in the price of the upgrade kit??
Well if it is RISC OS 4.39 AKA Adjust then I'll think you will find
that RISC OS 6 is the only actively worked on version of RISCOS Ltd's
stream. So it is a bit like buying an older version of Windows in that
any fix to that version that have been done to date will be available
and no new ones worked on abeit depending on if they are only
available via a Select subscription or not.
This gives you access to any Non Select subscription updates.
> OK... Brought the Upgrade kit from the RISC OS Ltd stand at the RUGOL
> show on the 3rd October... How do I register for the updates if
> they're included in the price of the upgrade kit??
If you mean the CD that upgrades RO4 to 4.39 or RO3.6/7 to 4.02 then you
don't. RO 4.39 is equivalent to the ROM 'Adjust' version which is now a few
years old and is perfectly stable and the CD contains the latest versions of
the various components applicable to the OS version.
If you want to upgrade (not 'update') from this point you really need to
move to RO6, and to get the latest version (6.16 ATM) you'd need to join the
Select scheme.
> > Using an IYONIX pc and RISC OS 5.14, the thinking person's
> > alternative operating system to Microsoft Windows.- Hide quoted
> > text -
> >
> > - Show quoted text -
^^^^^^^^^^^^^^^^^^^^^^^^^
Are you still copy and pasting the entire posting, even when you're
only replying to a small element of it? Please avoid that.
> OK... Brought the Upgrade kit from the RISC OS Ltd stand at the RUGOL
> show on the 3rd October... How do I register for the updates if
> they're included in the price of the upgrade kit??
They aren't. You have to subscribe to get updates.
B.
> In article
> <96000f86-ec1b-431c...@l35g2000vba.googlegroups.com>,
> Gazza <use...@garethlock.com> wrote:
>
> > > Select is a constantly moving target.
>
> [Snip]
>
> > OK... Where do I get essential updates without having to subscribe? Or
> > am I going to have to shell out another load of money to get these
> > fixes.
>
> Yeah!
>
> RISC OS 5 Open Source is the future!
Yeah!
OS6 has its enthusiasts just as OS5 does. At the respective sharp ends I
could easily form the impression that users of OS6.16 and those interested
in ROOL's latest could be quite evenly matched.
There has been speculation elsewhere about the distribution of platform
usage. To add to that how many have moved from the Iyonix to VRPC. I have.
The problem ROOL has is that there is no currently available platform for
their OS. The Iyonix is no longer, OS5 on modern hardware is still work in
progress as is OS5 on rpcemu. The counter to that, and the advantage that
ROOL does have is, the open sourcing of its code which opens up new areas of
programming interest. Those whose abilities are elsewhere, non-programmers
that is, can continue to do what they have done for years, using PipeDream
and the other wonderful RISC OS applications, on VRPC which has just the
right number of bits for some older software.
A future I would be happy with is to have a Mac OS5 emulation to go with the
OS4.39 VRPC already on this Mac.
--
David Pitt
Snow Leopard - MessengerPro
> The problem ROOL has is that there is no currently available platform for
> their OS. The Iyonix is no longer, OS5 on modern hardware is still work in
> progress as is OS5 on rpcemu.
Whoa, hold your horses. No, the BeagleBoard port is not finished, but
it is substantially complete, and is quite different to "no currently
available platform for their OS". It seems pretty reasonable that it
will be completed in the fullness of time, and that it should then
work with small changes on both Pandora and Touch Book.
The only "problem" here is that it's largely being done by one
person in their spare time. The reasons for that are an entirely
different discussion.
> David Pitt wrote:
>
> > The problem ROOL has is that there is no currently available platform
> > for their OS. The Iyonix is no longer, OS5 on modern hardware is still
> > work in progress as is OS5 on rpcemu.
>
> Whoa, hold your horses. No, the BeagleBoard port is not finished, but it
> is substantially complete, and is quite different to "no currently
> available platform for their OS". It seems pretty reasonable that it will
> be completed in the fullness of time, and that it should then work with
> small changes on both Pandora and Touch Book.
Moving on then, I see recent progress on the Beagle Board front :-
http://www.riscos.info/index.php/BeagleBoard-based_Laptop
Some other relevant links :-
http://www.alwaysinnovating.com/touchbook/
> Not much has happened since then, especially for ViewFinder users.
We've got the keyboard shortcuts, sliding menus and CIELAB in RISC OS
6, not to mention a RISC OS 6 native ViewFinder drivers (okay only 1
card supported and apparently not to it's maximum resolution either).
> In message <7j4kubF...@mid.individual.net>
> Steffen Huber <sp...@huber-net.de> wrote:
>
> > Not much has happened since then, especially for ViewFinder users.
>
> We've got the keyboard shortcuts,
In the Filer, I assume. But this was already nearly provided by dozens
of third-party apps. I assume you mean keyboard navigation in the
filer?
> sliding menus
Nobody's explained to me why anybody would ever want this yet :)
> and CIELAB in RISC OS 6,
What is CIELAB?
B.
> On Thu, 08 Oct 2009 18:22:30 +0100 Paul Stewart
> <pauls...@phawfaux.co.uk> wrote:
>
> > We've got the keyboard shortcuts,
>
> In the Filer, I assume. But this was already nearly provided by dozens of
> third-party apps. I assume you mean keyboard navigation in the filer?
Yes, it does a Windows-style "move the selection around with the keyboard"
type of thing, from what I've seen.
> > sliding menus
>
> Nobody's explained to me why anybody would ever want this yet :)
It solves the problem that SmartMenu solved several years ago (using Acorn's
solution from RISC OS 3): what if you open the menu tree too close to the
right-hand side of the screen? :-)
--
Steve Fryatt - Leeds, England
> Rob Kendrick <nn...@rjek.com> wrote:
What is the problem? We have always had a menu over the TaskManager
icon at the right hand edge of the screen. If the submenu handling
(which can occasionally be a bit tricky but that does not happen that
often) was really that much of a problem, then surely, people would
have been crying out for a solution for almost two decades. I find the
sliding very annoying and disruptive. Why would I want the menu over
the TaskManager to slide in slowly from the right ending up in the
very same position where it appears instantly on other RISC OS
versions? Why would I want it to slide around like mad while I am
trying to move the pointer from one submenu arrow to the other and why
does the OS have the insolence of moving the pointer, which is only
for me to control using the mouse?
Configure => Windows => Windows => Menu slide Speed => Off.
What a relief. ;-)
Obviously, your mileage may vary. Maybe there are others who find this
useful, I just do not like it at all. But then, since you can switch
it off, nothing is lost, but it is not exactly a feature I would call
a big improvement.
Martin
--
---------------------------------------------------------------------
Martin Wuerthner MW Software http://www.mw-software.com/
ArtWorks 2 -- Designing stunning graphics has never been easier
spam...@mw-software.com [replace "spamtrap" by "info" to reply]
Which nicely proves my point, as all of these are not really "big"
features in my book - at least compared to the Select 1 & 3 features
I named.
> In message <mpro.kr7ukt01...@stevefryatt.org.uk>
> Steve Fryatt <ne...@stevefryatt.org.uk> wrote:
>
> > Rob Kendrick <nn...@rjek.com> wrote:
>
> > > On Thu, 08 Oct 2009 18:22:30 +0100 Paul Stewart
> > > <pauls...@phawfaux.co.uk> wrote:
>
> > > > sliding menus
> >>
> > > Nobody's explained to me why anybody would ever want this yet :)
>
> > It solves the problem that SmartMenu solved several years ago (using
> > Acorn's solution from RISC OS 3): what if you open the menu tree too
> > close to the right-hand side of the screen? :-)
>
> What is the problem? We have always had a menu over the TaskManager icon
> at the right hand edge of the screen. If the submenu handling (which can
> occasionally be a bit tricky but that does not happen that often) was
> really that much of a problem, then surely, people would have been crying
> out for a solution for almost two decades.
Indeed. Sorry, I was replying in a similar way to Rob's post, and I suspect
my point got lost in the medium.
Skliding menus seem to me to be 'visual bling', but otherwise offer little
that RISC OS 3 + SmartMenu hasn't made available for a few years (plus the
fact that the existing solution does what it does without sliding the menus
around).
> In message <7j4kubF...@mid.individual.net>
> Steffen Huber <sp...@huber-net.de> wrote:
>
> > Not much has happened since then, especially for ViewFinder users.
>
> We've got the keyboard shortcuts, sliding menus and CIELAB in RISC OS
> 6, not to mention a RISC OS 6 native ViewFinder drivers (okay only 1
> card supported and apparently not to it's maximum resolution either).
>
> Regards
Don't feed the trolls.
There are some people around here and other forums (the usual supsects) that
will put down anything ROL do / have done since Castle put out RO5. The
market is polorised.
Unfortunately, much of the comment on forums of various kinds doesn't
necessarilly reflect the views of all users because many have long since
given up on the silly arguments which keep occurring.
I don't often post to (or read) the newsgroups etc. now for that reason.
Steve.
--
StevePotts at blastzone DOT demon STOP co DOT uk (www.blastzone.demon.co.uk/)
Written on RISC OS.
http://www.riscos.com/
> In message <b8d91da...@phawfaux.co.uk>
> Paul Stewart <pauls...@phawfaux.co.uk> wrote:
>> In message <7j4kubF...@mid.individual.net>
>> Steffen Huber <sp...@huber-net.de> wrote:
>>
>>> Not much has happened since then, especially for ViewFinder users.
>>
>> We've got the keyboard shortcuts, sliding menus and CIELAB in RISC OS
>> 6, not to mention a RISC OS 6 native ViewFinder drivers (okay only 1
>> card supported and apparently not to it's maximum resolution either).
> Don't feed the trolls.
Steve, this must be a bad joke - unless I misunderstand what you are
trying to say here. You cannot possibly have called Steffen a troll?
One of our most technically knowledgeable developers who, sadly, posts
very rarely here? Of course, you may or may not agree with his
opinions, but that is no justification for such an accusation.
> >> We've got the keyboard shortcuts, sliding menus and CIELAB in RISC
> >> OS 6, not to mention a RISC OS 6 native ViewFinder drivers (okay
> >> only 1 card supported and apparently not to it's maximum
> >> resolution either).
>
> > Don't feed the trolls.
>
> Steve, this must be a bad joke - unless I misunderstand what you are
> trying to say here. You cannot possibly have called Steffen a troll?
> One of our most technically knowledgeable developers who, sadly,
> posts very rarely here? Of course, you may or may not agree with his
> opinions, but that is no justification for such an accusation.
Developers rarely agree with users on aspects like this. Developers
tend to like to see under-the-bonnet improvements done before bling,
and this is certainly one of the polarised differences between
Select/Adjust and RISC OS 5.
B.
They aren't. Select subscribers get updates as they've paid £99 * X
years for their copy, standalone users got a lastest-version-at-the-time
for about £49, but if they want a later one they have to pay again.
---druck