1.Is there any way to stop the percentage timer appearing every time you open a omniscope file..As this itself must take up quite a lot of computation power ??
2.In datamanager the Omniscope block always repeats every change that the developer has applied to the coloumns/file since the creation of the file.Is there any way to delete all changes (i.e prevent Omniscope from running through the changes) and just keep the current settings.Currently you can delet individual changes but this is a long and dubious process since you have to delet them individually.Is it possible to have checkboxes of whch ones you would like to see included or excluded. Please see example below to make things clearer.
Suppose i have a new omniscope file and say have coloum1,coloumn 2 from a database and then create formulae fields say formul1,formulae2.Now say i delete formuale 2 and rename formuale 1 to formulae 11.Now say i changes formuale in formulae11 and rename the field formulae 12.
In omniscope it will run all these changes sequencitally every time you open the file.Is there any way just to keep the current coloumns/formulae field changes . I.e Coloumn 1, Delete column 2,formulae12
As currently i would have to delete each operation seperately in the omniscope block.But for files which go under a lot of development this is not ideal to do as it takes a lot of time.
I.e So either it would be good to have a tickbox to delet include changes in the omniscope block or just have a button which says keep changes to create current field/coloumn settings.
1. No, and no it doesn't. It is negligible, and the idea (that progress display shouldn't hinder progress) has of course been considered. We reduce the frame rate on single-core PCs; on multi-core PCs, there are always some spare processor cycles for its modest requirements.
2. If you expand the Omniscope block aren't you able to remove the unnecessary actions individually? If you're in the same session that performed the actions, you'll be given two options for this. If not, only "remove by refresh" will be available. Either way, it allows you to remove actions which were subsequently not needed, only executing the changes when you next click Load or refresh from source.
However the point of DataManager is to avoid this kind of problem altogether. You use the Field Organiser and other operations to transform your data and configure it in a non-sequential / free-form way, without building up a history of mistakes.