Emanuele Mazza

The working dir is for patches that loads other files in some of his objects, having a data/ folder ( i called it like this to maintain some relation with...

Well, the write is not over the entire xml file, if you check the ```saveConfig(bool newConnection)``` function, you'll see that opens the file, traverse it and only access and rewrite...

Oh, so i always misunderstood the DOM buffer, well, better later than never, thanks for the clarification! The ```none``` is not the absolute path of the patch file, is the...

Yes, i was preoccupied by that, but i too think the incompatibility with previous versions is inevitable. For the filepath, yes, is a custom object var, used only by a...

Thanks for searching for better options, it seems that the best choice is to stay on TinyXML and ofxXmlSettings Adding some features as sandboxing and maybe some better logic, i'm...

Ok then, we'll switch to PugiXML then, maybe we can write some methods to have it imitating ofxXmlSettings functions, so the port will be super easy?

I've pulled some basic api for ofxPugiXML https://github.com/Daandelange/ofxPugiXML/pull/1 to mimic ofxXmlSettings and simplify the future Mosaic port

Just discovered that pugixml 1.9 is included in OF0.11, and ofXml class is based on that, maybe we could extend the class and use that instead of the ofxAddon?

Hi Daan, i think maybe it would be better, on one side, to add an ofPixel outlet to the VideoGrabber object, with some toggle in the object interface to enable/disable...

You're right, it's better to not alter the number of VideoGrabber object to preserve older xml/patch compatibility, and yes, the internal default is **pixels** but for the sake of usability...