Kajus Posted February 14, 2019 Report Share Posted February 14, 2019 Hi, is there any specific reason why gwinPrintg function can only be used if the gfile is enabled (and therefore also one of the file backends as the compilation fails with no backed enabled). I find this function quite handy, but as I don't use ugfx filesystem api, I don't want to enable the whole gfile stuff... Thanks you, Jakub Link to comment Share on other sites More sharing options...
inmarket Posted February 14, 2019 Report Share Posted February 14, 2019 GwinPrintg uses the internal printg framework which requires gfile. GwinPrintg effectively creates a pseudo file based on each window. This in practice is a very efficient use of code reuse. For now enable GFILE and the "string" sub-system as that enables sprintf equivalent functionality and the string sub-system is tiny. I will look at how easy it is to change the code so it can either be used without GFILE or at least without any sub-module file-systems turned on. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now