reorg/modify table bug

[JD Kromkowski]

For future release in Personal 1. If you reorganize you lose your display settings. basically you get I guess default settings. 2. The modify table thing does really work correctly with respect to display settings. You actually have to manually change the cell to what you want. 3. Importing from csv, etc in Personal also still a problem accepting time values. JDK

[Michael]

On 17/07/2013 17:52, kromkowski wrote:
> For future release in Personal
>
> 1. If you reorganize you lose your display settings.
>
> basically you get I guess default settings.

Not sure what you mean by your display settings, what is changing? If you mean things like the table grid column layout, those are
not preserved across closing and opening of a table, so yes, currently they would be lost.

> 2. The modify table thing does really work correctly with respect to
> display settings. You actually have to manually change the cell to what
> you want.

?

> 3. Importing from csv, etc in Personal also still a problem accepting
> time values.

Are you import merging, or importing to new table? If to new table, then you would have to convert the data in date, time, and
datetime fields to appropriate integer values first. That is an area where we could improve, I agree. Potentially we could do this
change ourselves.

Ciao, Neil

[JD Kromkowski]

On 07/18/13 7:18 AM, Neil Robinson wrote:
> On 17/07/2013 17:52, kromkowski wrote:
>> For future release in Personal
>>
>> 1. If you reorganize you lose your display settings.
>>
>> basically you get I guess default settings.
>
> Not sure what you mean by your display settings, what is changing? If you mean things like the table grid column layout, those are
> not preserved across closing and opening of a table, so yes, currently they would be lost.

No I mean display settings (DisplayFormat perhaps is the correct term)
for fields like "hh:mm am" or "mm/0d/yyyy" or "3 U"

Create a SB file (See attached)

Fields

TimeField
DateField
CapString
StringField

Convert using "Superbase to Simpol Converter".

Open the datasource and table in Personal.

Modify Table

Scroll the grid over to where you see DisplayFormat.

Make note and cancel (close the modify form window)

Reorganize to TEST2. Note the difference! All of the display formats
are changed, even the string fields.

Try to change the date and time displayformats, with your buttons.
Doesn't work.

The only way to change the display is to actually go into the cell and
type the format and then get out of cell (lose focus) and click OK or Apply.

Now export (File|Export) table to csv. Close all the tables.

Now import (File|Import) the csv to a new file.

All the fields have been changed to txt!

Close everything.

Open up the TEST1 datasource and test1 table.

Remove all the data.

Now import (File|Import) the csv to that file, i.e. merge with original
existing table (the one that has time and datefields.

You will think nothing actually imported (so thisis a bug), but it
actually import except that time and date fields have no data in them!

Click table view and you will see.
Change back to record view (CRASH!).

Reopen Personal and open table – you'll see no data in the time and
date fields.

JDK

>> 2. The modify table thing does really work correctly with respect to
>> display settings. You actually have to manually change the cell to what
>> you want.
>
> ?
>
>> 3. Importing from csv, etc in Personal also still a problem accepting
>> time values.
>
> Are you import merging, or importing to new table? If to new table, then you would have to convert the data in date, time, and
> datetime fields to appropriate integer values first. That is an area where we could improve, I agree. Potentially we could do this
> change ourselves.
>
> Ciao, Neil

[Peter Barus]

Neil,

Just testing to see if I got on here…

Peter

On Thu, 18 Jul 2013 07:18:20 -0400, Neil Robinson <neil@simpol.com> wrote:

> On 17/07/2013 17:52, kromkowski wrote:
>> For future release in Personal
>>
>> 1. If you reorganize you lose your display settings.
>>
>> basically you get I guess default settings.
>
> Not sure what you mean by your display settings, what is changing? If
> you mean things like the table grid column layout, those are
> not preserved across closing and opening of a table, so yes, currently
> they would be lost.
>
>> 2. The modify table thing does really work correctly with respect to
>> display settings. You actually have to manually change the cell to what
>> you want.
>
> ?
>
>> 3. Importing from csv, etc in Personal also still a problem accepting
>> time values.
>
> Are you import merging, or importing to new table? If to new table, then
> you would have to convert the data in date, time, and
> datetime fields to appropriate integer values first. That is an area
> where we could improve, I agree. Potentially we could do this
> change ourselves.
>
> Ciao, Neil
>

—
Peter Barus

[Michael]

On 19/07/2013 17:38, kromkowski wrote:
> On 07/18/13 7:18 AM, Neil Robinson wrote:
>> On 17/07/2013 17:52, kromkowski wrote:
>>> For future release in Personal
>>>
>>> 1. If you reorganize you lose your display settings.
>>>
>>> basically you get I guess default settings.
>>
>> Not sure what you mean by your display settings, what is changing? If you mean things like the table grid column layout, those are
>> not preserved across closing and opening of a table, so yes, currently they would be lost.
>
> No I mean display settings (DisplayFormat perhaps is the correct term)
> for fields like "hh:mm am" or "mm/0d/yyyy" or "3 U"
>
> Create a SB file (See attached)
>
> Fields
>
> TimeField
> DateField
> CapString
> StringField
>
> Convert using "Superbase to Simpol Converter".
>
> Open the datasource and table in Personal.
>
> Modify Table
>
> Scroll the grid over to where you see DisplayFormat.
>
> Make note and cancel (close the modify form window)
>
> Reorganize to TEST2. Note the difference! All of the display formats
> are changed, even the string fields.
>
> Try to change the date and time displayformats, with your buttons.
> Doesn't work.
>
> The only way to change the display is to actually go into the cell and
> type the format and then get out of cell (lose focus) and click OK or Apply.

Hi John,

I finally stumbled over and was able to fix this bug. It turned out that although it was updating the grid cell, it wasn't
actually updating the property of the object that was holding this information.

> Now export (File|Export) table to csv. Close all the tables.
>
> Now import (File|Import) the csv to a new file.
>
> All the fields have been changed to txt!
>

As for this part, if you import CSV to a new table, then all of the fields /will/ be text, since there is no context. If you want
them to be something else, you need to have an empty table definition and then import merge the CSV data.

> Close everything.
>
> Open up the TEST1 datasource and test1 table.
>
> Remove all the data.
>
> Now import (File|Import) the csv to that file, i.e. merge with original
> existing table (the one that has time and datefields.
>
> You will think nothing actually imported (so thisis a bug), but it
> actually import except that time and date fields have no data in them!

Time and date information should now import merge properly.

> Click table view and you will see.
> Change back to record view (CRASH!).
>
> Reopen Personal and open table – you'll see no data in the time and
> date fields.

The new release has had a lot of fixes in very many areas. It is definitely worth a read through the 1.8-specific release notes,
as well as a look at some of the new chapters, libraries, samples, etc.

Watch for it, the release is going through final installation testing at the moment. It will be up in the next hour.

Ciao, Neil

>
>>> 2. The modify table thing does really work correctly with respect to
>>> display settings. You actually have to manually change the cell to what
>>> you want.
>>
>> ?
>>
>>> 3. Importing from csv, etc in Personal also still a problem accepting
>>> time values.
>>
>> Are you import merging, or importing to new table? If to new table, then you would have to convert the data in date, time, and
>> datetime fields to appropriate integer values first. That is an area where we could improve, I agree. Potentially we could do this
>> change ourselves.
>>
>> Ciao, Neil
>
>

[Author]

Posts