AtlasTooLargeException¶

Namespace Nfty.Core.Publish in assembly Nfty.Core.

public sealed class AtlasTooLargeException : InvalidOperationException

A Menu atlas would be larger than one image can be (a pixel ceiling on a side, or in area), so the write is refused rather than built.

Remarks¶

The refusal carries its two halves separately. AtlasTooLargeException.Problem is what is wrong and is true on any front-end; AtlasTooLargeException.Hint is the way out spelled for the command line. The CLI prints Message, which joins them, so its text is what it always was. A screen with its own Atlas/Loose tray shows AtlasTooLargeException.Problem and says "Choose Loose" in its own words, instead of leaking a flag that does not exist there.

It derives from InvalidOperationException because that is what the refusal threw before it had a type, so any caller that caught the base keeps working.

Constructors¶

AtlasTooLargeException(string)¶

public AtlasTooLargeException(string problem);

Creates the refusal.

Parameters

problem (string) - What is wrong, without an instruction.

Fields¶

CliHint¶

public const string CliHint = "write with --art loose instead.";

The way out as the command line spells it.

Properties¶

Hint¶

public string Hint { get; }

What to do about it, as the command line says it.

Problem¶

public string Problem { get; }

What is wrong: the atlas size and the limit it is past. No instruction in it.