Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cs.utexas.edu!ut-sally!utastro!werner From: werner@utastro.UUCP (Werner Uhrig) Newsgroups: comp.sys.mac Subject: Re: Finding out about the MultiFinder partition size of an application Summary: nope, that doesn't seem right ... Keywords: is it a feature - is it a bug??!! Message-ID: <2885@utastro.UUCP> Date: 11 Jul 88 22:15:38 GMT References: <2879@utastro.UUCP> <13689@apple.Apple.COM> Organization: U. Texas, Astronomy, Austin, TX Lines: 47 In article <13689@apple.Apple.COM>, goldman@Apple.COM (Phil Goldman) writes: > In article <2879@utastro.UUCP> werner@utastro.UUCP (Werner Uhrig) writes: <... this can be solved by always running MF. well, thanks a lot - when are the memory prices coming down? (-: < If the application is running under MF then the sizes are shown, but they > cannot be edited. well, either we are not talking about the same thing, or you are wrong. the GetInfo window does NOT SHOW the memory sizes of a running application. I just verified this and will send you a screen-dump on request. I am running VersaTerm-3.10 at this minute, so I went to the Finder-DeskTop, did a GetInfo on VersaTerm - it says the Memory sizes ar N/A. Then I did a COPY of VersaTerm and did a GetInfo on that, and the memory sizes of Copy of VersaTerm shows as 284k and 300k, respectively ... Maybe this version of VersaTerm doesn't have the latest new-fangled format of SIZE-resources or something ??!!.... but I believe that other applications show the same behavior ... Maybe you were thinking of the Finder-About-window showing the size of the partition the application is using? Maybe the reason why it shows N/A is that it was impossible to display a value in the GetInfo-window and still prevent the user from modifying it? or, maybe, it's a subtle way of telling the user that he can't change those values while running the application ?! well, dimming the field would have achieved that trick quite well also ... > These numbers are stored in the application's SIZE > resource in its resource fork. This cannot be modified while the application > itself might possibly do so. Unfortunately, the resource manager does > not support locking on a grain smaller than the entire fork. this is "too deep" for me and I don't quite understand its relevance ... -- ------------------------------------------------------------------------ send Email to: werner@rascal.ics.utexas.edu (Internet: 128.83.144.1) .....!ut-sally!rascal.ics.utexas.edu!werner should RASCAL be ill: werner@astro.as.utexas.edu or werner@utastro.UUCP)