CSV related problems

[Ewen Pring]

Here are some bug I can reproduce with Fireworkz v1.34/05 for RISC OS.

First I create a new file in a text editor. I simply use 2 test lines
of data as below. It is LF line terminated and saved as filetype CSV.

field1a,field2a
field1b,field2b

Double click on the CSV file from the filer, and assuming nothing else
tries to claim it before, Fireworkz runs and opens it. Here begin the
problems...

Problem 1. If the file has no DOS extension, Fireworkz treats it as
text, despite it being filetyped as CSV in RISC OS. So the comma
de-lineated fields are not put in adjacent cells. However, if it has a
"/CSV" suffix, Fireworkz opens up the "Loading CSV" dialogue and I can
choose to insert, overwriting blank cells etc, as expected.

Problem 2. If Fireworkz was already running, a new Fireworkz icon is
loaded onto the icon bar for each CSV file double clicked on.

Problem 3. Assuming I've got around problem 1, the file is displayed
OK and everything seems to work as expected. BUT if I save the sheet
in Fireworkz format, then re-open that saved Fireworkz format file, I
get TWO identical windows opening (except the second has a " 2" suffix
at the end of the name in the window title bar). Not only that, but
every cell in each window contains two copies of the text that is
supposed to be in that cell. For example cell A1 contains
"field1afield1a". This makes the document unusable.

None of the above 3 problems happen if instead of double clicking on
the CSV file from the filer, I instead drag the CSV file from the
filer onto an already running Fireworkz icon bar icon.

For info the relevant lines in !Fireworkz.!Boot and .!Run are;

If "<File$Type_DFE>"="" Then Set File$Type_DFE CSV
SetMacro Alias$@RunType_DFE Run <Fireworkz$Dir>.!Run %%*0

Best regards

--
Ewen Pring, St. Albans, Herts
using Iyonix, RISC OS 5.18
http://www.timebus.co.uk/riscos/

[Chris Johnson]

In article <ac5b107...@iyonix.timebus.co.uk>,

Ewen Pring <ewen....@physics.org> wrote:
> None of the above 3 problems happen if instead of double clicking
> on the CSV file from the filer, I instead drag the CSV file from
> the filer onto an already running Fireworkz icon bar icon.

> For info the relevant lines in !Fireworkz.!Boot and .!Run are;

> If "<File$Type_DFE>"="" Then Set File$Type_DFE CSV
> SetMacro Alias$@RunType_DFE Run <Fireworkz$Dir>.!Run %%*0

Looks like Fireworkz is not claiming the dataload/open message for
filetype DFE so the filer is then filer running the csv file, which
causes a new incarnation of Fireworkz to be run.

--
Chris Johnson

[Stuart Swales]

Yup - that's the cause.

Fireworkz' core policy is to not claim non-native files, but the !Run
file does... If would help if it behaved consistently, so I propose to
make the core claim the same (CSV, XLS, WK1) files as does !Run.

Stuart

--
Stuart Swales