Hello Viktor
Viktor Szakáts wrote:
>
>> 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.
-----
enjoy hbIDEing...
Pritpal Bedi
_a_student_of_software_analysis_&_design_
--
View this message in context:
http://n2.nabble.com/hbide-testing-go-2-tp4671197p4690674.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
