It has to work also for people who are not using only one setting for the entire project.
I have had a discussion with a Logic user about how Logic seemingly can display the qquantize settings. Turns out it can… until it cannot. Once the user starts to change quantization not on a track or part level the displayed settings suggest a quantization that does not match reality anymore.
My understanding is there are 2 levels of MIDI quantization in Logic: (1) region based quantization; (2) note based quantization - and that (2) overrides (1).
The region based quantization setting are shown in the inspector when a MIDI region is selected on any track in the project. If you drag a MIDI region to some other MIDI/instrument track in the project, it should display whatever the regions current quantize, etc. settings are in the inspector. No use of a MIDI editor, piano roll like display or manual selection of notes is necessary to quantize MIDI data at the region based level. Perhaps another way to think of it is every region can start off with its own (and perhaps different) quantization or grid settings (which can be recalled). You can see the region based quantize controls available in the inspector at, Logic Pro advanced quantization parameters - Apple support (MM)
Now if you subsequently open that MIDI region in Logic’s piano roll MIDI editor, select some notes, and quantize them to something different then the region parameters, then the note based quantize settings for the selection will be retained (and override the region based Q settings) for those notes. It seems correct for finer grained, note based quantization settings to not be reflected in the region inspector.
I don’t see a way in Cubase to recall the current quantize settings per note (or per region) from what I have seen. If everything in a region were quantized to the same value, then perhaps it could be displayed in the Cubase info line as discussed here, Display and set quantization parameters per MIDI region (regardless of track) - #5 by snm. I have sometimes resorted to sorting MIDI regions in Cubase across multiple tracks - according to a different setting of the real-time MIDI quantize plugin on each track. It requires more tracks, but helps to map what each region uses for Q settings.