Ghostkeeper d8a066c1e7 Increment instance container version number instead of just quality_changes ... Otherwise when we load that quality_changes file we'll deny it because the instance container version number is wrong. Contributes to issue CURA-5054.		2018-03-09 16:14:24 +01:00
..
fabtotum_abs_fast.inst.cfg	Increment instance container version number instead of just quality_changes	2018-03-09 16:14:24 +01:00
fabtotum_abs_high.inst.cfg	Increment instance container version number instead of just quality_changes	2018-03-09 16:14:24 +01:00
fabtotum_abs_normal.inst.cfg	Increment instance container version number instead of just quality_changes	2018-03-09 16:14:24 +01:00
fabtotum_nylon_fast.inst.cfg	Increment instance container version number instead of just quality_changes	2018-03-09 16:14:24 +01:00
fabtotum_nylon_high.inst.cfg	Increment instance container version number instead of just quality_changes	2018-03-09 16:14:24 +01:00
fabtotum_nylon_normal.inst.cfg	Increment instance container version number instead of just quality_changes	2018-03-09 16:14:24 +01:00
fabtotum_pla_fast.inst.cfg	Increment instance container version number instead of just quality_changes	2018-03-09 16:14:24 +01:00
fabtotum_pla_high.inst.cfg	Increment instance container version number instead of just quality_changes	2018-03-09 16:14:24 +01:00
fabtotum_pla_normal.inst.cfg	Increment instance container version number instead of just quality_changes	2018-03-09 16:14:24 +01:00
fabtotum_tpu_fast.inst.cfg	Increment instance container version number instead of just quality_changes	2018-03-09 16:14:24 +01:00
fabtotum_tpu_high.inst.cfg	Increment instance container version number instead of just quality_changes	2018-03-09 16:14:24 +01:00
fabtotum_tpu_normal.inst.cfg	Increment instance container version number instead of just quality_changes	2018-03-09 16:14:24 +01:00