At 1:21 PM +0200 on 4/26/02, Herbie Gluender wrote: >Dear Heather, > >part of what you are going to do is already present with >my "CustomChoose"-Demos that show functionally equivalent >solutions with an old style dialog and NavServices preCarbon >and Carbon. In my latest announcement to this list >(Wednesday 24.April, message #30824) I already discussed >some peculiarities with the Carbon solution under OS 9.x, >OSX-Classic and OSX native. > >You may download the "CustomChoose-Demo"-Combo from the DropBox. I haven't had a chance to look at the preCarbon stuff but I have looked at the project you sent me off-list. It's very nice and well polished. It is functionally equivalent to the C code I ported from the WASTE project. It uses custom controls, DITLs and custom event and filtering callback procedures. Your code will pave the way for custom menus, radio buttons and checkboxes in these dialogs boxes. It's pretty unlimited the number of configurations you could make. I was trying to work on something similar a while back but abandoned it as too complex. It's really great for a custom dialog solution but what I wanted was a solution that could extend the present NavServices portion of the FILE$ runtime function, be backward compatible with older FB code and the ability to be configured on the fly. I think I've done all that, it works well in Standard, and Appearance compliant builds for both Carbon and preCarbon compiles. Thanks for the inspiration though, in order to extend things further I'm going to modify the NavGetFolder feature and add the NavGetObject feature as well. That will require using a new type constant so we would have: fileName$ = FILES$(_fObject...) Unfortunately, what I'm not trying to do at this moment is support Navigation Services 3.0 but mostly because it's not well documented and some features are MacOS X only. -- Heather Donahue -- non sum qualis eram