Unsure if this is a known issue or not (I assume that either it is or that I’m just overlooking something).
It seems that when saving Guides in a project, the changes are not actually stored. Attaching a GIF to illustrate what I’m seeing.
Edit: Oh, I wonder if this may be a classic case of manual neglect on my part. I just realized that Guides and Markers are managed together (at least to some extent). I didn’t notice that from the menus until just now (and yes, I’m reading through the relevant sections of the manual). I’m still a little unsure about how that plays into what I’m seeing here, however.
Hmm, I seem to have painted myself into a corner somehow. In my KDL settings I have a healthy set of categories, but in addition to not being able to save project categories as shown above, when I open the Add Marker dialog the category names and colors don’t match what’s in my KDL settings (despite being the correct categories).
I wonder if this may be related to the fact that when the project was originally created, I didn’t have any category definitions in place?
IIRC, there was an issue with saving marker and guide categories and a bug report was logged. Could you please go over to bugs.kde.org and create one for your scenario? You may want to search for guides in the bug list or pay attention to the bug tracker suggesting similar bug reports when you create yours. Thanks!
Ah, good suggestion. I should have been poking around in there in the first place. Will do so going forward.
Could this be related to 477617 (resolved 2023-12-02)?
(Fwiw, that issue was for a different platform/version; I’m on Windows 10 Frameworks 6.0.0, Qt 6.6.2)
That was the one I had in mind, yes. Platform does not matter, version may, in particular as it was closed, apparently. Perhaps a regression was introduced that you just found 
I suggest you log a bug report regardless …
No problem, and done. I included a comment at the end of the summary mentioning that project-specific guides are not saving (in any scenario, it seems). Should I go ahead and create a bug report for that as well? (Sorry if that seems like the obvious thing to do, just trying to proceed carefully.)
