mirror of
https://github.com/ajisaacs/OpenNest.git
synced 2026-11-06 04:46:13 -05:00
Priority worked like a rank (lower first) with a default of 0, and the Edit Drawing form stopped at 0, so moving one part ahead of the rest meant renumbering every other drawing. Higher-first lets a user raise a single part to 1 and leave everything else at the default. Every engine, filler and candidate comparer now serves the highest tier first. Stored values keep their order: - .nest files add `nestPriority` and keep writing the negated value under `priority`, so older readers nest in the same order; files without `nestPriority` are negated on read. Drawing packages strip both, so package hashes are unchanged. - Library settings send both keys the same way for older clients. - Server schema v18 negates stored drawing priorities (an older server refuses the upgraded database). - Job documents move to version 2; version 1 jobs are converted, and an older worker refuses version 2 instead of reversing the order. The Edit Drawing form now accepts negative priorities and says higher numbers nest first. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
13 lines
463 B
C#
13 lines
463 B
C#
namespace OpenNest.Api;
|
|
|
|
public class NestRequestPart
|
|
{
|
|
/// <summary>Optional stable requirement identity. NestRunner derives part-{requestIndex} when omitted.</summary>
|
|
public string Id { get; init; }
|
|
public string DxfPath { get; init; }
|
|
public int Quantity { get; init; } = 1;
|
|
public bool AllowRotation { get; init; } = true;
|
|
/// <summary>Nesting order: higher numbers nest first.</summary>
|
|
public int Priority { get; init; } = 0;
|
|
}
|