At 16.09 -0500 1999.03.25, Mark Yannuzzi wrote: >> So essentially: >> >> DEFAULTLOCATION is just a path. I believe it is converted to an AEDesc for >> you. > >If you pass a null string, the dialog opens with the last visited location. Right. I was just pointing out that the docs for Nav Services says you need to pass an AEDesc, and apparently the module coverts it to an AEDesc for you. >> DIALOGOPTIONS is a data structure object (a good way to start is with >> NavGetDefaultDialogOptions) that is changed with: >> >> $options->somefield($somedata) > >Would this be true for the NavDialodOptionsFlags also? I can see that for >setting the option you might use: > > $options->dialogOptionFlags(kNavSelectAllReadableItem) > >but how would you reset it? I think for setting it, it would be more like: $flags = $options->dialogOptionFlags; $flags |= kNavSelectAllReadableItem; $options->dialogOptionFlags($flags); method(value) actually sets it to the value, it does not add a value. You could probably "shorten" it with: $options->dialogOptionFlags ( $options->dialogOptionFlags() | kNavSelectAllReadableItem ); And to reset it, maybe: $options->dialogOptionFlags(kNavDefaultNavDlogOptions); None of the above code is tested, caveat scriptor. Oops, I just wrote this and saw you figured it out. :) >A few questions: > >1) I assume that you must supply an event handling procedure to get the >window title bar to display. Is this correct? I don't know. >2) I wanted to pull the filter procedure outside the NavGetFile call, but >when I did (defining it before the call), I get the following error: > > # Can't call method "fileInfo" without a package or object reference. > >Since it I thought that Mac:: packages exported there types and functions, >this was a surprise error. I tried adding Mac::Navigation::, but got the >same error. Should it be possible to define the FILTERPROC subroutine >outside the NavGetFile function? Did you use Mac::Files? If so, I don't know what the problem would be. That's where the fileInfo structure is from. >3) I have discovered that the second element ($_[2]) passed by NavGetFile to >the FILTERPROC appears to be the filterMode variable (NavFilterModes type), >which is "...a list of objects currently being filtered." How would one use >this, as it appears that it is not necessary for one to check that the >Browser list (kNavFilteringBrowserList = 0) is currently being filtered >before the filter is applied? I don't know. I didn't use it for anything, and didn't find it necessary. Though if you find a need for it, I am sure we can figure out how to use it. :) -- Chris Nandor mailto:pudge@pobox.com http://pudge.net/ %PGPKey = ('B76E72AD', [1024, '0824090B CE73CA10 1FF77F13 8180B6B6']) ===== Want to unsubscribe from this list? ===== Send mail with body "unsubscribe" to macperl-request@macperl.org