You do have a point there. I dono. I just felt a little bad. I don't like inconveniencing people if I can help it. You're right though, I reckon. I guess it is there job after all.

Chris.

----- Original Message ----- From: "E.T." <ancient.ali...@icloud.com>
To: <macvisionaries@googlegroups.com>
Sent: Saturday, July 04, 2015 5:51 PM
Subject: Re: Boy did I get myself in a predicament earlier today!


Chris,
   Let me se if I can put this in a different prrspective.

   Forgetting the devepor angle, assume that Yosemite is still in
development even tho El Capitan may be released in just 2-3 months.
Maybe Apple has no plans to release anything further for Yosemite. Does
not matter.

   If Accessibility is willing to write a ticket, that is fine as it
stheir job. Whether ti goes beyond that is of no importance. You
submitted a bug report, its now Apple's to do whatever they want with it.

From E.T.'s Keyboard...
   ancient.ali...@icloud.com
Many believe that we have been visited
in the past. What if it were true?

On 7/4/2015 2:23 PM, Christopher-Mark Gilland wrote:
The reason I called Accessibility was because I am not running the beta
of Yosemite, only that of El Capitan, therefore, I should be covered
with their support.  Second off, I didn't know if this was a bug, or if
it was just me not knowing what I was doing.  Thirdly, it generally
takes engineering a while to write back.  In my case, I needed to try
getting an answer as quickly as possible.
Finally, is it really a bad thing me calling Apple Accessibility since
I'm a dev?  Does that fulfit my right to ask them questions?
Sorry, but now, I'm very confused.
Chris.

    ----- Original Message -----
    *From:* Yuma Decaux <mailto:jamy...@gmail.com>
    *To:* macvisionaries@googlegroups.com
    <mailto:macvisionaries@googlegroups.com>
    *Sent:* Saturday, July 04, 2015 5:17 PM
    *Subject:* Re: Boy did I get myself in a predicament earlier today!

    Chris,

    I’m not sure what exactly you are trying to achieve in the context
    of contacting apple’s general accessibility desk  when you can get
    on with the developer program, as you’ve mentioned you have, and
    start bug reporting on yosemite’s beta program as some might not
    make the switch once it goes public, though this is definetely not
    what is recommended as the new OS is mainly focused on performance.

    The best method for reporting each of your bugs is to first fill in
    the descriptive form offered by feedback assistant, then add an
    audio example to demonstrate the issue. Apple’s engineers will
    immediately find it very helpful and understand the problem as you
    explain the process. The fact that you are sending a feedback form
    and not talking to a lower level apple support tech will increase
    your chances of having the issue resolved.

    Cheers,







    On 5/07/2015, at 7:05 AM, Christopher-Mark Gilland
    <clgillan...@gmail.com <mailto:clgillan...@gmail.com>> wrote:

    First off, before I say anything, let me start by wishing everyone
    a very very! happy, and safe forth.  God bless America!
    OK, anyway, here is my concern.  I'd be curious how you all would
    a handled this.  I was trying to do something in Yosemite earlier
    today.  I can't really go into the specifics of what.  You'll know
    why in a second.  Come to find out, this something worked just
    fine in Mavericks, but apparently Apple broke Voiceover
    accessibility in this one area within Yosemite.  Well, the thing
    is, I didn't realize that it had been busted in Yosemite.  I
    thought, like mavericks, it still worked, as this isn't exactly
    the most common feature in the OS that I've had to access.  The
    thing is, I am an Apple developer.  On one of my test machines,
    I'm running the developer beta preview of El Capitan.  In El
    Capitan, the issue I was facing has been fixed.  I just happened
    at the time to be at my Yosemite production machine instead.  So,
    I called Apple Accessibility to see if maybe I was missing
    something.  It was then determined that this has been broken since
    the official first release of Yosemite.
    Well, obviously, I'm on NDA, and from what Developer Support has
    told me,  most of the senior advisors in the Accessibility
    department are not devs, therefore, it is advised not to discuss
    with them any of the stuff that is covered under NDA.  This means,
    I couldn't exactly say, no big deal, it's fixed in El Capitan.
    I'll just wait until it's released, and all will be golden.  The
    advisor starts to open a ticket feedback case request to
    engineering to figure out if this issue can be fixed in a future
    OSX release.  I felt so! bad!  On the one hand, I knew he was
    waisting his time doing this, as it has! been fixed, but, yet, I
    really couldn't say anything.
    This made me really uneasy.  I hate waisting people's time.  So,
    what should I have done?  I wound up just letting him create the
    ticket, but I feel really bad doing so and bothering engineers
    with something which already has been addressed.
    Chris.

    --
    You received this message because you are subscribed to the Google
    Groups "MacVisionaries" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to macvisionaries+unsubscr...@googlegroups.com
    <mailto:macvisionaries+unsubscr...@googlegroups.com>.
    To post to this group, send email to
    macvisionaries@googlegroups.com
    <mailto:macvisionaries@googlegroups.com>.
    Visit this group at http://groups.google.com/group/macvisionaries.
    For more options, visit https://groups.google.com/d/optout.

    --
    You received this message because you are subscribed to the Google
    Groups "MacVisionaries" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to macvisionaries+unsubscr...@googlegroups.com
    <mailto:macvisionaries+unsubscr...@googlegroups.com>.
    To post to this group, send email to macvisionaries@googlegroups.com
    <mailto:macvisionaries@googlegroups.com>.
    Visit this group at http://groups.google.com/group/macvisionaries.
    For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google
Groups "MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to macvisionaries+unsubscr...@googlegroups.com
<mailto:macvisionaries+unsubscr...@googlegroups.com>.
To post to this group, send email to macvisionaries@googlegroups.com
<mailto:macvisionaries@googlegroups.com>.
Visit this group at http://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To unsubscribe from this group and stop receiving emails from it, send an email to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at http://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups 
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at http://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/d/optout.

Reply via email to