Onyx Rip Queue annoyance..

[SWCL]

In v.7.0.6 the rip queue - as in the actuall queue, was oraganised really well.

The latest jobs that had been printed were sent to the bottom of the storage area - bumping the older jobs up one as it went..

Recyclable was at the bottom - archived stuff was at the top, again automatically arranged so the most recently printed jobs were at the bottom of that section..

Print/Rip failures nestled in between these two sections rather neatly as well...


So why oh why oh why, does 7.1 not do the same thing???

Seems to have a mind of its own compared to the previous version!

Even when I click the time colomn, then the status column (which is how I asume the previous version worked) - it does not remember where I want it to put the job I just printed

Even just clicking the time column on its own - arranging everything in the storage to arrange itself so the most recently printed job is at the bottom..

I print another job without pressing any other column & that job gets put somewhere totally random - not on the bottom where I want it!

I even watched it reorganise the jobs by itself having clicked time & left it...

How can I have a quick an easy workflow like 7.0.6 when I have to hunt for previously printed files!

Has anyone got any ideas how I can arrange my jobs & keep them arranged the way I want them!!!

Chris.

[ScottyDoo]

Let me talk to the engineers and find out what's changed. That's an annoyance of mine as well. When it comes time to start alpha/beta testing the next release I'll specifically take a look at that part as well.

[ScottyDoo]

I asked and they said they found a bug listed in the system that said that it doesn't remember the sort type after restarting Rip-Queue, but mentioned nothing of the behaviors you mention here.

They added these details to this bug so it will be addressed on the next build.

[SWCL]

No help to me at the moment then, but thanks for passing on the fault so its hopefully fixed in the next build.

[ScottyDoo]

Originally Posted by SWCL

No help to me at the moment then, but thanks for passing on the fault so its hopefully fixed in the next build.

Yeah, sorry, was the best I could do =)