On Apr 27, 2006, at 12:33 PM, Sven E Olsson wrote:
On 27 apr 2006, at 20.00, Norman Palardy wrote:
On Apr 27, 2006, at 11:44 AM, Sven E Olsson wrote:
So you mean, that all other apps on my machine using an another
os, than my RB built app on the same machine?
Not quite clear on what you mean.
Nearly every app on my machine when I save has the "Hide
Extension" check box.
The only
ones that do not are much older Carbon apps like CodeWarrior 8 and
GraphicConverter 4.
I believe these may be using an older API that brings up a
different dialog hat does not include this setting.
If they use an another API, then it is depending witch API is used,
not depending on the OS (I mean if it exist or not)
And the older API looks to have more features that the new one. (If
i compare Photoshop/RB or TextWrangler/RB)
I'd actually assume it's a matter of which particular function in the
API they used.
And, "Hide Extension" is just a user preference as to whether the
extension is shown in the Finder.
Since it's user selectable set the default name for the save
dialog and let the user decide if they want to see the extension
or not.
Yes I know, but if it was possible to turn it off, I and many
others should be happy.
This apps NOT showing an 'Hide Extension checkbox'
1 - The old Simple Text have NOT (Carbon)
2 - TextWrangler have NOT (Cocoa I think, have nib files inside the
bundle)
3 - skEdit have NOT (looks like Cocoa)
4 - Photoshop CS have NOT (Carbon ?)
5 - Image Ready have NOT (Carbon ?)
So it looks NOT depending on the OS i use (OS 10.4.6)
Screen shot skEdit: http://www.xhtmlsoft.com/rb/saveas.png
I never said it had anything to do with which version of the OS.
OS X supports numerous calls, some from new API's & some from older
ones. Carbon has a number of methods for similar things. If you use
one function you may get one behavior or appearance, and if you use a
different one you get a different appearance. And if you happen to be
running a Cocoa application it may appear different again because
it's a different API.
If a developer is using an older API they may NOT get the Hide
Extensions box. If they are using the newer ones they may.
At least that's my guess at why you see this. I've seen this before
with Classic Mac OS API's as they brought out newer ones with more
functionality.
Norman Palardy
OS X 10.4.6 / MacBook Pro 2.16Ghz MHz / 1Gb RAM
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>