Bug 380766

Summary: Fixed in git: Setting number of decimal places in precision doesn't work
Product: [Applications] rkward Reporter: RKWard Team <rkward-devel>
Component: generalAssignee: RKWard Team <rkward-devel>
Status: RESOLVED FIXED    
Severity: normal CC: thomas.friedrichsmeier
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: All   
Latest Commit: Version Fixed In:

Description RKWard Team 2013-09-25 15:43:27 UTC
-- Originally posted by (AT sourceforge.net): asalber --

-- This ticket was imported from http://sourceforge.net/p/rkward/bugs/132 on 2017-05-30 15:26:58 +0100 --
When I define a new numeric variable I set the precision indicating the number of decimal places, but it' doesn't work. 


rk.sessionInfo()
RKWard version: 0.6.1
KDE version (runtime): 4.10.5
KDE version (compile time): 4.9.5
Local KDE directory: /home/alf/.kde/
RKWard storage directory: /home/alf/.rkward/

Debug message file(s) in use (these may contain relevant diagnostic output in case of trouble):
/tmp/rkward.frontend.jd3344
/tmp/rkward.rbackend.TJ3352

R version (compile time): 3.0.0  (2013-04-03 r62481)
R runtime session info:
R version 3.0.1 (2013-05-16)
Platform: i686-pc-linux-gnu (32-bit)

locale:
 [1] LC_CTYPE=es_ES.UTF-8          LC_NUMERIC=C                 
 [3] LC_TIME=es_ES.UTF-8           LC_COLLATE=es_ES.UTF-8       
 [5] LC_MONETARY=es_ES.UTF-8       LC_MESSAGES=es_ES.UTF-8      
 [7] LC_PAPER=es_ES.UTF-8          LC_NAME=es_ES.UTF-8          
 [9] LC_ADDRESS=es_ES.UTF-8        LC_TELEPHONE=es_ES.UTF-8     
[11] LC_MEASUREMENT=es_ES.UTF-8    LC_IDENTIFICATION=es_ES.UTF-8

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base     

other attached packages:
[1] rkward_0.6.1
Comment 1 Thomas Friedrichsmeier 2016-01-01 16:25:18 UTC
- **summary**: Setting number of decimal places in precision doesn't work --> Fixed in git: Setting number of decimal places in precision doesn't work
- **status**: open --> open-fixed
Comment 2 Thomas Friedrichsmeier 2016-01-01 16:25:18 UTC
Finally fixed (in the development version).

Thanks for reporting!