CI / Build and test (pull_request) Failing after 2m3s
CI / PostgreSQL 16 integration (pull_request) Skipped
CI / PostgreSQL 17 integration (pull_request) Skipped
CI / Docker image (pull_request) Skipped
CI / Windows tests and installer (pull_request) Skipped
CI / YAML check (pull_request) Successful in 4s
The owner renamed the product and moved the repository to the self-hosted Gitea (https://gitea.encke-hake.ts.net/BalboSoft/Chronos) for more control, and asked for Actions and a first automatic release with the server package and the Windows exe (docs/requests/2026-10-23-chronos-gitea.md). - Chronos everywhere: a byte-exact rename of contents and paths, then a per-language review of the forms the old name's ending had dictated. - Gitea instead of GitHub: the update check, licence, issue and support links read ChronosReleasesUrl; the update check takes the highest stable version, offers a pre-release build its final release and reports a repository it cannot see as a failed check. EULA, security policy and Gitea issue forms live at the repository root. - Gitea Actions for the Linux act_runner (.gitea/workflows): CI, release, nightly image and performance gates in the .NET SDK container with git checkout. The release cross-compiles the Windows programs, checks their icon, version and DPI manifest, packs installers and zips, publishes the Gitea release and pushes the server image (REGISTRY_TOKEN). Windows-only tests run in an opt-in job on a Windows runner (WINDOWS_RUNNER). - New Chronos.Tools commands: zip, gitea-release, postgres-ci (replaces the docker-exec script, which Gitea's service containers do not allow) and pe-check. BREAKING CHANGE: programs, settings, data folders, file types, environment variables and the Docker image use the new name; nothing is migrated from Titano, which never had a release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
35 lines
1.0 KiB
C#
35 lines
1.0 KiB
C#
using Chronos.Testing;
|
|
using Chronos.Ui.Visuals;
|
|
|
|
namespace Chronos.App.Tests.Visuals;
|
|
|
|
public sealed class PixelGridTests
|
|
{
|
|
[Theory]
|
|
[Case(1.0)]
|
|
[Case(1.25)]
|
|
[Case(1.5)]
|
|
[Case(2.0)]
|
|
public void HairlinesCoverWholeDevicePixels(double scale)
|
|
{
|
|
var thickness = PixelGrid.SnapThickness(1, scale);
|
|
var devicePixels = thickness * scale;
|
|
Assert.Approximately(Math.Round(devicePixels), devicePixels, 1e-9);
|
|
for (var v = 0.0; v < 50; v += 0.37)
|
|
{
|
|
var centre = PixelGrid.SnapLine(v, thickness, scale) * scale;
|
|
var left = centre - devicePixels / 2;
|
|
Assert.Approximately(Math.Round(left), left, 1e-9, $"v={v}");
|
|
Assert.LessOrEqual(Math.Abs(centre - v * scale), 1);
|
|
}
|
|
}
|
|
|
|
[Test]
|
|
public void SnapRoundsToDevicePixelBoundaries()
|
|
{
|
|
Assert.Approximately(10, PixelGrid.Snap(10.2, 1), 1e-12);
|
|
Assert.Approximately(10 + 2 / 3.0, PixelGrid.Snap(10.6, 1.5), 1e-12);
|
|
Assert.Approximately(3.3, PixelGrid.Snap(3.3, 0), 0);
|
|
}
|
|
}
|