Activity log for bug #1168877

Date Who What changed Old value New value Message
2013-04-14 13:16:03 MC Return bug added bug
2013-04-14 13:16:09 MC Return compiz: assignee MC Return (mc-return)
2013-04-14 13:18:13 MC Return description The <precision> tag in the .xml files will not work for int values. It gets ignored. The <precision> tag in the .xml files will not work for int values. It gets ignored. The definition seems to be: typedef struct _CompOptionIntRestriction { int min; int max; } IntRestriction; in src/privateoption.h
2013-04-14 13:19:40 MC Return compiz: status New In Progress
2013-04-14 13:53:12 MC Return compiz: status In Progress New
2013-04-14 14:42:44 MC Return description The <precision> tag in the .xml files will not work for int values. It gets ignored. The definition seems to be: typedef struct _CompOptionIntRestriction { int min; int max; } IntRestriction; in src/privateoption.h The <precision> tag in the .xml files will not work for int values. It gets ignored. The definition seems to be: typedef struct _CompOptionIntRestriction {     int min;     int max; } IntRestriction; in src/privateoption.h Note: This will require a patching of several files, it does not seem to be trivial. As workaround we could use floats that get converted to ints by Compiz afterwards, so a float with precision 5.0f would be read and converted to (int) later...
2013-06-15 22:55:03 MC Return compiz: importance Undecided Low
2013-06-15 22:55:10 MC Return compiz: milestone 0.9.10.0
2013-07-04 08:02:55 MC Return description The <precision> tag in the .xml files will not work for int values. It gets ignored. The definition seems to be: typedef struct _CompOptionIntRestriction {     int min;     int max; } IntRestriction; in src/privateoption.h Note: This will require a patching of several files, it does not seem to be trivial. As workaround we could use floats that get converted to ints by Compiz afterwards, so a float with precision 5.0f would be read and converted to (int) later... The <precision> tag in the .xml files will not work for int values. It gets ignored. The definition seems to be: typedef struct _CompOptionIntRestriction {     int min;     int max; } IntRestriction; in src/privateoption.h Note: This will require a patching of several files, it does not seem to be trivial. As workaround we could use floats that get converted to ints by Compiz afterwards, so a float with precision 5.0f would be read and converted to (int) later. This workaround is now tested and works perfectly as expected, so for example a percent setting can be expressed as min 0.0f, max 100.0f, precision 5.0f and in the code we can do a: int percent = (int) optionGetPercent ();
2013-07-04 08:03:31 MC Return summary CCSM: <precision> tag just works for float, but not for int CCSM: <precision> tag just works for float, but not for int, a workaround is known and tested
2013-07-22 06:43:55 Sam Spilsbury compiz: milestone 0.9.10.0 0.9.10.2
2013-07-24 11:52:41 MC Return compiz: milestone 0.9.10.2 0.9.11.0