Bug#305245: v.digit: Next not used should be called Auto increment
AFAIK the next not used could also be an ID (cat) with lower value than the current which would not be Auto increment but Auto decrement. -- Markus Neteler neteler itc it http://mpa.itc.it/markus/ ITC-irst - Centro per la Ricerca Scientifica e Tecnologica MPBA - Predictive Models for Biol. Environ. Data Analysis Via Sommarive, 18- 38050 Povo (Trento), Italy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305245: v.digit: Next not used should be called Auto increment
Ok, my assumtion was wrong but Hamish explained it earlier. Still next not used makes more sense. Markus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305245: v.digit: Next not used should be called Auto increment
So the action is truely Next not used and not Auto increment. So, closing this bug could be considered appropriate? H Dan, anything further? Sure: please document that somewhere, e.g., in v.digit.html. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305245: [Pkg-grass-devel] Bug#305245: v.digit: Next not used should be called Auto increment
On Tue, Apr 19, 2005 at 12:23:45PM +1200, Hamish wrote: Package: grass Version: 6.0.0-1 Followup-For: Bug #305245 The mode Next not used should be called Auto increment. the exact behavior in vector/v.digit/var.c: cat = cat_max_get ( var_geti(VAR_FIELD) ) + 1; var_seti ( VAR_CAT, cat ); So if you manually digitize cat 10 then the next feature as cat 1, then switch to Next not used mode the next feature will be 11 not 2. This way 9 features later you don't inadvertently make something else 10 as well. So the action is truely Next not used and not Auto increment. So, closing this bug could be considered appropriate? -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305245: [Pkg-grass-devel] Bug#305245: v.digit: Next not used should be called Auto increment
On Tue, Apr 19, 2005 at 12:23:45PM +1200, Hamish wrote: ps - upstream bugs are best filed, discussed, and dealt with in the upstream bug tracker where all the upstream developers will at least see them: http://grass.ibiblio.org/bugtracking/bugreport.html It is common practice to forward this kind of bug to the appropriate upstream email/list, and tagging the report +upstream, forwarded and whatever needed. This is one of the maintainer's tasks. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305245: [Pkg-grass-devel] Bug#305245: v.digit: Next not used should be called Auto increment
On Tue, 2005-04-19 at 09:58 +0200, Francesco P. Lovergine wrote: On Tue, Apr 19, 2005 at 12:23:45PM +1200, Hamish wrote: ps - upstream bugs are best filed, discussed, and dealt with in the upstream bug tracker where all the upstream developers will at least see them: http://grass.ibiblio.org/bugtracking/bugreport.html It is common practice to forward this kind of bug to the appropriate upstream email/list, and tagging the report +upstream, forwarded and whatever needed. This is one of the maintainer's tasks. Which I would normally be doing. But I've been too busy lately to go over these bugs. Anyone is welcome to forward and tag these reports as they see fit. Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305245: v.digit: Next not used should be called Auto increment
Package: grass Version: 6.0.0-1 Followup-For: Bug #305245 The mode Next not used should be called Auto increment. the exact behavior in vector/v.digit/var.c: cat = cat_max_get ( var_geti(VAR_FIELD) ) + 1; var_seti ( VAR_CAT, cat ); So if you manually digitize cat 10 then the next feature as cat 1, then switch to Next not used mode the next feature will be 11 not 2. This way 9 features later you don't inadvertently make something else 10 as well. So the action is truely Next not used and not Auto increment. So, closing this bug could be considered appropriate? Dan, anything further? Hamish -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305245: v.digit: Next not used should be called Auto increment
Package: grass Version: 5.7.0+6.0.0beta2-1 Tags: upstream Severity: minor File: /usr/lib/grass/bin/v.digit The mode Next not used should be called Auto increment. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305245: v.digit: Next not used should be called Auto increment
Package: grass Version: 6.0.0-1 Followup-For: Bug #305245 The mode Next not used should be called Auto increment. the exact behavior in vector/v.digit/var.c: cat = cat_max_get ( var_geti(VAR_FIELD) ) + 1; var_seti ( VAR_CAT, cat ); So if you manually digitize cat 10 then the next feature as cat 1, then switch to Next not used mode the next feature will be 11 not 2. This way 9 features later you don't inadvertently make something else 10 as well. So the action is truely Next not used and not Auto increment. Hamish ps - upstream bugs are best filed, discussed, and dealt with in the upstream bug tracker where all the upstream developers will at least see them: http://grass.ibiblio.org/bugtracking/bugreport.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
