mirror of
https://github.com/storytold/vectorcraft.git
synced 2026-11-17 22:33:08 +00:00
The active color settings are process-wide. A test on another thread that sets them, or opens a document with its own profiles, can change them between two renders of a canvas test. Frame keys hold the guide color converted through the settings, and effect rasters are made again when the settings change, so the second render no longer matched the first. a_drag_over_a_wide_blur_draws_the_blur_from_the_still_frame and cached_frames_keep_their_scale_during_resize_rotation_and_dpi_changes failed this way in full parallel runs of the crate's tests. - The 20 canvas tests that compare two renders (frame keys, raster reuse or pixels) now run inside cms::with_active with the settings that are active when they start (keeping_color_settings). - The tests that ran a real render worker and waited up to 60 seconds for its frames (the wide blur drag, the drag with raster effects and the turned view) use a controlled worker. The test thread renders its jobs with render_worker::render, the function the worker thread now calls. - The placed bitmap test waits for the bitmap without a 20-second limit or sleeps.