Bug 270207

Summary:	Cannot enter positive value (credit) for operations in my account
Product:	[Applications] skrooge	Reporter:	hcoohb
Component:	general	Assignee:	Stephane MANKOWSKI <stephane>
Status:	RESOLVED FIXED
Severity:	normal	CC:	stephane, trent.niemann
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	25.1.0
Platform:	Chakra
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description hcoohb 2011-04-06 11:28:47 UTC

Version:           unspecified (using Devel) 
OS:                Linux

I cannot enter a positive value for an operation...
I am trying to put +33 for example, but when I click "add" or "modify" skrooge always put -33 for this operation...
And this is the same for every amount I put,  skrooge always made it negative...
The weird thing is that I tried several times in a new document as well...and sometimes it works wometimes not...
I am using Chakra with testing repositories (so with kde 4.6.2)

Reproducible: Sometimes

Steps to Reproduce:
enter positive value for an operation
apply

Actual Results:  
skrooge put a negative value.
(sometimes it works though, but I couldn't find a way to reproduce 100%)

Expected Results:  
positive value

The console only shows this line :
QObject::connect: Connecting from COMPAT signal (QComboBox::textChanged(QString))

Comment 1 Stephane MANKOWSKI 2011-04-06 15:43:14 UTC

What is your Skrooge version ? (You can find it in about panel)

Comment 2 hcoohb 2011-04-06 15:50:38 UTC

Sorry, I missed that, it's skrooge 0.8.1

Comment 3 Stephane MANKOWSKI 2011-04-06 22:45:20 UTC

Git commit d8a69d3db8f841a7102a18cc9d0d62bd64276d84 by Stephane Mankowski.
Committed on 06/04/2011 at 22:50.
Pushed by smankowski into branch 'master'.

BUG: 270207: Cannot enter positive value (credit) for operations in my account

M  +1    -0    CHANGELOG     
M  +3    -1    skgbasegui/skgcalculatoredit.cpp     

http://commits.kde.org/skrooge/d8a69d3db8f841a7102a18cc9d0d62bd64276d84

Comment 4 hcoohb 2011-04-14 13:08:39 UTC

I rebuilt skrooge with 0.8.1 and just the patch you mentioned above and I can confirm this commit fixed the bug !
Thank you for the reactivity ! :)