[electrotap] zipping a standalone with tap tools...

[Peter]

On OSX, I made a standalone. It uses 2 tap objects (tap.folder and
tap.path). I tested it. It works. I zip it up. I then unzip it, and
try the app file that came from the zip. I get an error that there is
no such object as tap.folder or tap.path...
What is going on?

Peter.

--
You received this message because you subscribed to the Electrotap group.
To unsubscribe from this group, send email to electrotap-...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/electrotap?hl=en

Electrotap -- http://electrotap.com/
Tools for Innovative Music, Media, and Art

[Morgan Sutherland]

Sometimes when I unzip files, it asks me what encoding I want to use (UTF, Mac Roman, etc.)

Perhaps it has something to do with this?

[Timothy Place]

Hi Peter,

Is the unzipping on the same computer as the zipping?  That sounds bizarre, unless there are resource forks getting stripped -- but that shouldn't be the case for recent versions.  Can you give me more information about what versions of various things (OS, Max, Tap.Tools) you are using?  Thanks.

best,
 Tim

[Peter Castine]

I could be wrong, but it might make a difference *how* you're zipping. Compress "«filename»" from the Finder’s context menu does some magic that keeps Mac-specific file info intact, whereas zip/gzip & Co. in the Terminal, being Unixy, are more pure (and sometimes less helpful for MacOS bundles). 

Wildly guessing -- P.

[Peter]

OS X 10.58, Max 5.14 (42462), TT 3.01 Pro. Unzipping is on the same
computer, and on different computers. Same result - tap objects not
found. You can try it and it see it not working with this build:
http://lividserver.com/dl/cell/CellDNA_v203beta8-OSX.zip
As for "how" I'm just right clicking on the folder, selecting
"compress" then renaming the zip. I suppose I could try it from
terminal if you need me to Tim. My current workaround for distributing
is to create a compressed .dmg file from Disk Utility rather than a
zip file.
Pete.

[Timothy Place]

Hi Peter and all,

I've confirmed that this problem is fixed in the Tap.Tools 3.1 release candidate (coming later today).

best,
  Tim