Current testing

[BenAW]

It seems a lot of time and discussion is spent on problems arising from trying to work with IM5 while it is ingesting, indexing or doing other background tasks. This isn't very productive in finding real bugs imo.
So I propose for the time being to lock the user interface while IM5 is doing any of the above tasks.
Real problems only related to those tasks will be apparent then.
Once most bugs are gone and Mario has had time to tweak IM5 for speed, it would be useful to consider releasing the user interface again. Perhaps only for systems that have a minimum processer speed and/or number of processors and have a sufficiently fast hard disk where the dbase is stored.

Another point is re-creating dbases. It could very well be that problems created by old and solved bugs are still popping up in the current dbases. So I propose to force a re-creation of the dbases for the next build as well.   

[cytochrome]

...

Another point is re-creating dbases. It could very well be that problems created by old and solved bugs are still popping up in the current dbases. So I propose to force a re-creation of the dbases for the next build as well.

And how to re-create the DB making sure one does not drag settings, panels/biews etc from the previous DB, so dragging along the possible source of these bugs?

I ask because Mario often said there should be no need to re-create aDB, my present base is circa 60000 files and with my relatively slow PC I am not keen to start this again with each IM revision.

But I am willing to do it now because I have still some problems with diacritic characters in metadata.

Francis

[Gerd]

Hi,
unless Mario did us not tell to create a new database, I will not do it!

[Richard]

The Beta Version is not fit to be used on a production system!

Be prepared to delete and re-create the IMatch 5 test database.

Considering the above quotes I would not use more than 10,000 files for a test database.

[BenAW]

Hi,
unless Mario did us not tell to create a new database, I will not do it!

This used to be standard procedure for (almost) every new build in the early testing:
delete dbase and the .PTS file and create them from scratch. What would be the problem?

[BenAW]

And how to re-create the DB making sure one does not drag settings, panels/biews etc from the previous DB, so dragging along the possible source of these bugs?

Deleting the .PTS file should solve this.