On Monday, June 21, 2004, at 02:47  PM, tedd wrote:

>> On Sunday, June 20, 2004, at 07:46  AM, tedd wrote:
>>
>>> That's not as simple as I had hoped. The program works on the basis 
>>> of creating a region, monitoring the mouse and doing stuff when the 
>>> mouse is over, and/or clicks, within the region. Not that you said 
>>> it was, nor that I asked, but that's certainly not new nor simple.
>>
>> tedd,
>>
>> I'm not sure what you're envisioning, but what you describe is 
>> exactly how every button works--Appearance or non; X or 9: It creates 
>> a region (or rect), and tests to see whether the mouse is in that 
>> rgn. There's virtually no other way to do it. The fact that most of 
>> that process is generally hidden from the casual programmer doesn't 
>> change the fact that it's happening.
>>
>>  e-e
>>  =J= a  y
>>   "
>
>  =J= a  y:
>
> Apparently the misunderstanding is continuing, no doubt because I 
> didn't explain myself clear enough -- so let me try again.
>
> I realize that every button, or any control for that matter, is 
> determined by an interaction between the position of the mouse and a 
> region -- that's not at issue for this thread.
>
> What the basis for my original question was -- is there an "easy" way 
> to make an appearance button that looks and preforms like a web page 
> url link -- in other words, an underlined text that is clickable -- 
> sounds simple enough, don't you think?
>
> My reasoning is that considering that Apple released the Appearance 
> Button concept with a large number of "new" controls and a larger 
> number of deviations of those controls (like the many types of bevel 
> buttons for example) I thought that using one of those controls with 
> some combination of constants might make a link-like button.
>
> I was hoping for something simple like:
>
> appearance button _BtnID,,,,, Link", @r, _kControlBevelButtonNoFrame, 
> _kControlBevelButtonTextUnderlined
>
> My thought was that surely Apple must realize that browser have made 
> the "text-link control" a staple in the way end-users react with 
> computers and as such would have provided a way to capitalize on that 
> fact by providing a similar control. But apparently, as some here have 
> pointed out, Apple did not do that.
>
> Sorry for the confusion.

tedd,

Your question seems both clear and reasonable. Sorry if I read (and 
responded) carelessly. My guess is that an approach like Jonathan's is 
as close as we're likely to get, at least for now.

  e-e
  =J= a  y
   "

--
To unsubscribe, send ANY message to: futurebasic-unsubscribe@...