Age | Commit message (Collapse) | Author |
|
Since various apps can modify the type/creator of the files, we can't rely on the header of the resource fork to take the md5. I've therefore also recalculated all of the detector entries (all 5 of them) that use the Mac resource fork code.
svn-id: r55764
|
|
svn-id: r55403
|
|
svn-id: r54122
|
|
* names now comply to our naming conventions
* the function computeStreamMD5AsString which computes the MD5
as a hex string now returns it as a Common::String
* add doxygen comments
svn-id: r54121
|
|
Resource names can be the same across types (ie. 'PICT' "Foo" and 'snd ' "Foo"), so this ensures that the right type is chosen in those cases.
svn-id: r52756
|
|
It's now a static function since it doesn't require any local variables and is really separate from the resource fork code. Also, actually assigning the keycolor (which was just being ignored).
svn-id: r52075
|
|
memory leaks
svn-id: r49116
|
|
format in plain files
svn-id: r49074
|
|
svn-id: r49008
|
|
svn-id: r49004
|
|
resource fork. This introduces a new flag, ADGF_MACRESFORK, which when set will take the md5 and size from the resource fork instead of the data fork.
svn-id: r48997
|
|
svn-id: r48984
|
|
along the way.
svn-id: r47258
|