Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Cuetools 2.1.6 negative offset problem (Read 2927 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Cuetools 2.1.6 negative offset problem

Hi All

I've been trying out Cuetools 2.1.6 and I've come across this problem; it may be something I'm doing, but I wondered if anyone else can replicate it.

If I highlight the "offset" field when it contains "0" I can enter any positive offset, say 123.

If I do the same and try to enter -123 it comes up as 1230.

I can enter 123 and prepend ( if that's the word ) the minus sign.

Anyone else have this problem?

It's ok in 2.1.5, by the way.

Best Regards.
balr 2,0
using *,2

Cuetools 2.1.6 negative offset problem

Reply #1
Looks like the final version of 2.1.5 does this also.
korth

Cuetools 2.1.6 negative offset problem

Reply #2
Just had a look at my cuetools.exe and it's dated 02/07/2013, whereas the latest one is dated 12/05/2014.

Looks like the problem sneaked in after the level I have.

Any chance of fixing it in 2.1.6?

Best Regards.

Dizzy.
balr 2,0
using *,2

 

Cuetools 2.1.6 negative offset problem

Reply #3
The developer did read this topic. Can't speak for him so I don't know what priority it will have. There are workarounds.
korth

Cuetools 2.1.6 negative offset problem

Reply #4
OK - thanks for your interest.

As you say there are workarounds, so it's not really a problem.

If I'd have had the latest 2.1.5, I'd have got used to it and not bothered to mention it.

Best Regards.

Dizzy.
balr 2,0
using *,2