FontV any longer in use?

Is this software vector FontV any longer in use to redirect the FontManager?

Best Regards

Thomas Milius

Printers, perhaps?

Is FontV broken, not fit for purpose, or something?

Rummaging around in the sources, it looks like a bit of collusion between FontManager and the PDriver module.

When a print job is started, PDriver ¹ claims various vectors and events in order to track what is going on that might have relevance to the print job. It also broadcasts the Service_Print ServiceCall.

Here’s where FontManager gets involved. It will notice the ServiceCall and set printerflag appropriately. It will then, in the SWI handling ², blindly call TryPrinterDriver for each supported SWI. If printerflag and if not wimperrorflag then it will push the Font SWI number into R8 and pass all the data on to the PDriver_FontSWI SWI for it to be handled by the printer driver. And then it gets really convoluted. ;-)

¹ …Sources.Printing.Modules.PDModules.s.Core.Intercept

² …Sources.Video.Render.Fonts.Manager.s.Fonts01

Many thanks for your explanation.

However this doesn’t sound promising to me.

I want to examine the calls of the FontManager. It seens that the only chance would be to examine every SWI call before passing it to the original SWI handler :-(.

It is a bit strange that all other SWIs like ColourTrans, SpriteOp etc. can be properly traced/modified but not the FontManager inspite that a vector has been reserved for this.