QUOTE(ShadowFlare @ Dec 9 2006, 07:24 PM)
What it should do is if the file exists, try to open it as an mpq archive no matter what the extension is (be sure to use flags indicating only to open an existing file). If that doesn't work, then the file is not an mpq archive and does not contain one. BTW, as of SFMPQ version 1.06, saving to an embedded mpq archive works fine without any problems.
Okay, I will try and redo the loading routine to cope with this

QUOTE(ShadowFlare @ Dec 9 2006, 10:03 PM)
I don't think a "none" should be shown on the editor part of it, since it doesn't exist in the file, so you can't edit it. If a change is made to make the numbers match, I think it should just show the IDs as one number higher.
Simply displaying a higher ID is a no-brainer coding-wise, however I want to stay true to the purpose DatEd was made for - staying as faithful to the format as possible. I see two options here: (both would have a disclaimer in red that will state that the shown IDs are 1 off)
1)Implement the change into-the-core.
2)Make this an option in the Options box.
Hmm?
QUOTE(Voyager7456(MM) @ Dec 10 2006, 04:12 PM)
Refreshing the unit names after loading a TBL would be nice. (Right now you have to switch the views for the names to update).
Hokay, I'll try to do it for v1.4b.
QUOTE
I had another idea; could you make it so that a build time of 0 is written to the .dat as 1 of the old ArseIII units (1/15th of a second)? That way there'd be less crashes and those of us who need a 1/15th of a second value wouldn't need to use ArseIII to do it.
QUOTE(ShadowFlare @ Dec 11 2006, 10:54 PM)
Or maybe even an extra box for adding on a non-converted value to the build time from the existing box.
That's what I have in mind to do.There is enough space for it on the UI, and both options should be available.
QUOTE(Lord_Agamemnon(MM) @ Dec 11 2006, 07:35 PM)
Good job with the update, BK, and do you realize that DatEdit's almost a year old?
...and still kicking
QUOTE(Kookster @ Dec 13 2006, 12:13 AM)
I found another bug if you set a orders targeting to the first weapon entry, guass rifle(normal) it doesnt show that it is used by the order when on that weapon. This only applies to the first weapon entry as far as i can tell.
Will look into this.
QUOTE
I think Voys idea is best, cause the 0 is useless it makes starcraft crash if set to it.
This will go into the appropriate hint. DatEd does not include a SC-mod debugger as of now
PS:1000th reply is mine 