Here is a small app I made that one can use to create and modify .ini format files. I modeled it after Microsoft's Registry Editor since I figured most people will be familiar with its functionality.
Let me know if you think it needs any improvements.
(requires COMDLG32.OCX and MSCOMCTL.OCX )
Last edited by brenaaro; Dec 2nd, 2002 at 08:55 AM.
And I, for one, welcome our new insect overlords. I'd like to remind them as a trusted TV personality, I can be helpful in rounding up others to toil in their underground sugar caves.
That's pretty good. Just a couple of things - it seems to add some odd control characters or something at the end of key names (see attached image), and also why is that yellow thing down the bottoms. But great apart from that.
Hmm very interesting. The yellow bar is actually the back color of the form. I was using that to make sure that the bottom of the listviews reached the top of the status bar.
On my machine there was no yellow visible, but I'm using windows XP and it looks like you ran it on 9x? I'll have to redo that part. Also I didn't get any control characters, again it must be an XP thing. I'll take a look at it and post the source.
And I, for one, welcome our new insect overlords. I'd like to remind them as a trusted TV personality, I can be helpful in rounding up others to toil in their underground sugar caves.
Ok I uploaded the new exe in zip format (see original post's attachment). Can someone please try it on a win9x machine and let me know if that yellow bar and/or control characters appear? If they do I will have to wait until I get into work on Monday to solve that one...
I am also going to post some of the source code for the project. You'll note I avoided using API calls to do my reading and writing (WritePrivateProfileString, etc) because I find that they are too slow, and they did not provide all the functionality I needed.
There will be calls to subs and functions scattered throughout the code that may come up as undefined. These are mostly wrappers for API calls, or some of my own custom methods. Their names should be descriptive enough to tell you what they do (e.g; LoadFileContents(), WriteFileContents(), etc).
Last edited by brenaaro; Dec 2nd, 2002 at 08:55 AM.
And I, for one, welcome our new insect overlords. I'd like to remind them as a trusted TV personality, I can be helpful in rounding up others to toil in their underground sugar caves.
Fixed a couple of bugs relating to opening empty files. Original attachment has been updated.
Note: You can pass a filepath as an argument to the iniedit.exe
And I, for one, welcome our new insect overlords. I'd like to remind them as a trusted TV personality, I can be helpful in rounding up others to toil in their underground sugar caves.
Yeah I'm using Win 98SE. The yellow is still there in the compiled EXE. Also can you include the prj file in the source (too lazy to add the references and stuff ).
Originally posted by Rick Bull Yeah I'm using Win 98SE. The yellow is still there in the compiled EXE. Also can you include the prj file in the source (too lazy to add the references and stuff ).
Ok, I'm at work now so I'll try to fix that yellow bar and then re-upload it with the project file.
And I, for one, welcome our new insect overlords. I'd like to remind them as a trusted TV personality, I can be helpful in rounding up others to toil in their underground sugar caves.
Okay, I updated both attachments (iniedit.zip) and (source.zip). The yellow line should be gone for good.
There is one issue that I am aware of, that is that if your ini file has commented lines (starting with a ; ) then it doesn't work properly. I'll work on a fix for that when I get a chance and then upload it again.
Thanks for the feedback.
And I, for one, welcome our new insect overlords. I'd like to remind them as a trusted TV personality, I can be helpful in rounding up others to toil in their underground sugar caves.
Reply With Quote
).
