Hi Pritpal, >>> No. This cannot be. hbide.set is created by Qt's direct >>> function call which only accepts a filename. While reading it, >>> Qt expects a filename only. I cannot push these settings >>> at my own. It is a binary file by nature so it must been >>> moved from .ini extension to something else. Location was also >>> wrong. Now everything is fine. >> >> Hmmmmm. Yet it doesn't look very good. I wonder if there >> is a QT call which returns you the status as a binary >> stream, which you can do whatever you want (and same in >> reverse). It's very odd if an API forces file usage in such >> way. BTW it's not binary content. >> >> Well, I've tried and QT respects existing file, and >> will _add_ it's own content, so you can just safely use >> hbide.ini as the filename. >> > > It does, but then you did not inspect the contents of hbide.ini. > Qt re-writes the contents in pure .ini way which is not adopted > in hbide.ini strictly. I am manipulating it my own way. > So these remain to be two different files anyway. > > It is true that it is not binary content, but it is also equally > true that a programmer cannot change even a single byte. > When we comprehand .ini we have a notion that it is manually > editable. In this case I preceive it as binary though its format > is .ini.
I believe you all this, but it's very inelegant IMO to use two config files for above technical reasons. It's IMO our job to find proper solutions to such problems. IMO it's not a problem at all that binary encoded as text is included in any .ini file. Simply users won't be able to touch it, as they are not able to touch the exact same content in hbide.set. The other sad thing which I can read out from your words is that hbide.ini is not a standard .ini file but it's manipulate using some unique methods, which don't allow for extra content to be preserved. I think this should be fixed. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
