On Tue, 02 Jul 1996 11:08:07 -0600 David Thomas <ldthoma@uswest.com> wrote: > the problem with runtimes that lose the ability to have > files dropped on them is linked to the bundle bit. > When you move the runtime application to a machine without MacPerl, it > gets confused and, while you can double-click to start the > application, it will not recognize drag and dropping on the runtime. > This can be fixed by rebuilding the desktop of the volume you've moved > the runtime onto. It also blows away the nifty little camel icon(?). > I am still vauge as to why this is the case and would appreciate some > more insight into how this works. I haven't looked at either the MacPerl binaries or a runtime app, but one explanation for this would be that the icon resource is not in the runtime app but instead is relying on the icon from the MacPerl binary itself. Thus moving to a different disk loses the icon. The solution would be to write the icon to the runtime app itself. It might be reasonable to examine some of the packers like Stuffit or installers that make double-clickable objects to see how they manage their icons. It might be necessary to have a different "creator type" for the runtime apps than for MacPerl itself. Is anybody successfully using NetPresenz with MacPerl CGI that could give me a little orientation, or at least comment on whether my observations that an old MacPerl 4 CGI I wrote some time ago works with WebStar and MacHTTP and the Intercon server but not with NetPresenz is explainable? ---------------------- Charles B. Cranston <zben@ni.umd.edu> http:"//www.wam.umd.edu/~zben"