Ini functions

[GEOSoft]

I've been looking through one of my Backup CD's while I'm on the Road and I came across an INI UDF that I use.

It has

_INISort (which is really INI sort all)

_INISortSections (sort by section name)

_INISortValues (sort by key name)

_INIAddSection (allows you to add an empty section into an INI file for future use then sort it into place)

_IniCopySection (allows you to copy a complete section from one ini file to another)

_IniSortSectionByValue (sorts a section based on the data in the key value)

I use it to clean up some really long and messy INI files. The reason I haven't posted it before is because I want to modify _INISortValues to return a 2 dimension array. I'm not going to do that soon.

I had a request for it so here it is.

Ini.au3

EDIT: 01/19/2008 Code and demo replaced with a link and added a couple of functions.

Edited January 19, 2008 by GEOSoft

[ResNullius]

If anyone is interested then I'll post the code(it's all very short).

I'm interested. I work with ini files quite a bit and like them in an easy human readable format. I'd done an ini sort before, then started using a modification of one SmOke_N had written http://www.autoitscript.com/forum/index.ph...st&p=352917

I was going to get around to doing some more functions like you've mentioned, but hey, if they're already done (and probably better then I could do at this point) then "show me the code!"

[GEOSoft]

I'm interested. I work with ini files quite a bit and like them in an easy human readable format. I'd done an ini sort before, then started using a modification of one SmOke_N had written http://www.autoitscript.com/forum/index.ph...st&p=352917

I was going to get around to doing some more functions like you've mentioned, but hey, if they're already done (and probably better then I could do at this point) then "show me the code!"

OK, I added it to Post #1

Enjoy

[martin]

OK, I added it to Post #1

Enjoy

Great, thanks GEOSoft. I will definitely use this; I've often wished ini files were sorted but I never did anything about it.

Edited July 25, 2007 by martin

[GEOSoft]

Great, thanks GEOSoft. I will definitely use this; I've often wished ini files were sorted but I never did anything about it.

Thanks martin

I wrote it because one of my INI files was getting to be about the same size as the old win.ini file and I like to find things easily when I'm looking. I also added it as a tool in Project Express.

[ResNullius]

OK, I added it to Post #1

Enjoy

Thanks from me too!

These will definitely come in handy and I always appreciate seeing how others have tackled problems I too was looking to solve.

[GEOSoft]

Thanks from me too!

These will definitely come in handy and I always appreciate seeing how others have tackled problems I too was looking to solve.

Thank you

I just added a Demo script to the first post, primarily to show the usage of _IniSortValues() but all the functions except _IniAdd() are used.

[Zephir]

simple and awesome.... simply awesome

[GEOSoft]

simple and awesome.... simply awesome

Thank you.

I was just editing the first post when you replied so you might want to re-read it

[ResNullius]

Thank you

I just added a Demo script to the first post, primarily to show the usage of _IniSortValues() but all the functions except _IniAdd() are used.

Oh-Oh...

Just to be a pain-in-the-*** I took the following (admittedly slightly non-standard) sample ini file and ran it thru your demo.

[EMPTY]
EMPTY = Nothing

[@EMPTY2]
EMPTY2 = Nothing2

[.EMPTY3]
EMPTY3 = Nothing3

[-EMPTY4]
EMPTY4 = Nothing4

[YIKES]
A = ABCD
C = ABCDE
B = ABCDEF

[XYLOPHONE]
1 = ABCD
3 = ABCDEF
2 = ABCDE

[ZEBRA]
4 = Set to 3
5 = Set to 1

Choosing "ALL" produces this

[@EMPTY2]
EMPTY2=Nothing2

[7]

[EMPTY]
EMPTY=Nothing

[-EMPTY4]
EMPTY4=Nothing4

[XYLOPHONE]
2=ABCDE

[YIKES]
A=ABCD
B=ABCDEF
C=ABCDE

[ZEBRA]
4=Set to 3
5=Set to 1

As you can see, the "[.EMPTY"] section is dropped entirely and replaced by the mysterious "[7]". Some other Characters at the start of section names seem to be a problem too (like "#").

Also the "[XYLOPHONE]' section whose key names are all numbers drops all but one entry.

I'd have a go at seeing if I could fix it, but I thought maybe you should get first go GEOSoft

Edit: fixed punctuation

Edited July 25, 2007 by ResNullius

[GEOSoft]

Oh-Oh...

Just to be a pain-in-the-*** I took the following (admittedly slightly non-standard) sample ini file and ran it thru your demo.

[EMPTY]
EMPTY = Nothing

[@EMPTY2]
EMPTY2 = Nothing2

[.EMPTY3]
EMPTY3 = Nothing3

[-EMPTY4]
EMPTY4 = Nothing4

[YIKES]
A = ABCD
C = ABCDE
B = ABCDEF

[XYLOPHONE]
1 = ABCD
3 = ABCDEF
2 = ABCDE

[ZEBRA]
4 = Set to 3
5 = Set to 1

Choosing "ALL" produces this

[@EMPTY2]
EMPTY2=Nothing2

[7]

[EMPTY]
EMPTY=Nothing

[-EMPTY4]
EMPTY4=Nothing4

[XYLOPHONE]
2=ABCDE

[YIKES]
A=ABCD
B=ABCDEF
C=ABCDE

[ZEBRA]
4=Set to 3
5=Set to 1

As you can see, the "[.EMPTY"] section is dropped entirely and replaced by the mysterious "[7]". Some other Characters at the start of section names seem to be a problem too (like "#").

Also the "[XYLOPHONE]' section whose key names are all numbers drops all but one entry.

I'd have a go at seeing if I could fix it, but I thought maybe you should get first go GEOSoft

Edit: fixed punctuation

Thanks I'll look at it again. Was that running the Demo script or calling the functions individually. The demo was pulled from one of my apps that uses the functions so I may have screwed up the conversion of the Demo. I ran it this morning against a long ini file and it was fine. If it had screwed up that file I would have been choked except that it does create a backup.

Edit

Backup a second here. The Ini file that you sent to it has spaces before and after the "=". That won't work. Any Ini function will fail then. After the "=" should be ok Though.

I'll take a look anyway

Edited July 25, 2007 by GEOSoft

[SmOke_N]

Nice work GeoSoft... I find making the functions I use to follow AutoIt's standards is most helpful if I'm going to share my work (or I just keep making Res keep editing my work )... the Ini* functions do catch the information if there is a space before or after the = sign though ...

Edited July 25, 2007 by SmOke_N

[GEOSoft]

Nice work GeoSoft... I find making the functions I use to follow AutoIt's standards is most helpful if I'm going to share my work (or I just keep making Res keep editing my work )... the Ini* functions do catch the information if there is a space before or after the = sign though ...

Thanks Smoke

I thought that a space before was taboo. Oh well I'm looking to mod it now. It hasn't failed me at all, and these are not new functions, but my Ini files never have the spaces.

[SmOke_N]

Thanks Smoke

I thought that a space before was taboo. Oh well I'm looking to mod it now. It hasn't failed me at all, and these are not new functions, but my Ini files never have the spaces.

Yeah, mine don't either... but you have to "idiot" proof it sometimes ... keep up the good work.

[GEOSoft]

As you can see, the "[.EMPTY"] section is dropped entirely and replaced by the mysterious "[7]".

That 7 is being caused by _ArraySort I can solve that.

I think The same may apply to the rest I'm just not sure why it runs my files OK. That error should persist throughout.

[GEOSoft]

@ResNullius

I know the answer and I know the why so now I'm happy and I will post the modifications in a while and notify @everyone when it's done. I just want tho look at that Demo again first.

The problem was this

The Array.au3 file that I #include for my self is not the standard Array.au3 file. Some of the functions have been modified to suit me and one of those is _ArraySort(). That's why it works for me and why It failed For you.

The 7 was actually Array[0] which in the code you posted was the number of elements.

My _ArraySort already has $i_Descending = 0 AND $i_Base = 1

So the proper call to _ArraySort() using the standard UDF is _ArraySort(<Array>, 0, 1)

[GEOSoft]

Yeah, mine don't either... but you have to "idiot" proof it sometimes ... keep up the good work.

I agree but it would be a real bummer if I had to add error handleing for a simple INIRead().

I've got the problem now anyway.

[ResNullius]

Yeah, mine don't either... but you have to "idiot" proof it sometimes ... keep up the good work.

"idiot" proof it sometimes... we wouldn't be implying anything now would we?

[GEOSoft]

"idiot" proof it sometimes... we wouldn't be implying anything now would we?

Never!!!

Do you really think that Smoke or I would single out an individual as an "IDIOT"? Well we probably would but we would never mention names. We're smarter than that.

Give me 5 minutes and the new code will be up.

[GEOSoft]

Post #1 has been updated to reflect the corrections in the _ArraySort() calls

I also now have a sample on that page thanks to ResNullius.

Next time I'll just let him fix it too.

BTW @ResNullius

That ini code wasn't mixed up enough for a good test so I modified it a bit so at least you can see some sorting by comparing to the result. But thanks for noticing the problem. I might have gone on thinking that because it worked for me that it was fine.

Edited July 26, 2007 by GEOSoft