Comments for Ask Different Blog http://apple.blogoverflow.com Ask Different - answers for your Apple questions Tue, 01 Mar 2016 11:50:43 +0000 hourly 1 https://wordpress.org/?v=4.5.6 Comment on Allowing iOS 9 and El Capitan questions by Lisa Coffey http://apple.blogoverflow.com/2015/08/beta-ios-9-and-el-capitan-questions-allowed/#comment-649266 Tue, 01 Mar 2016 11:50:43 +0000 http://apple.blogoverflow.com/?p=1718#comment-649266 That also brings up the fact that if there are fewer community members actually participating in the public beta, then the onus of fielding those questions will fall on a small number of participants. Those participants are likely the more experience members, possibly moderators and developers with a wealth of knowledge on all things Apple, and then Beta questions will take up time that they could be using in the forum answering questions that would benefit from their expertise and would have longer lasting usefulness.

http://www.fixithere.net/apple-customer-service/

]]>
Comment on App Update Review: Hanging With Friends by Smyls http://apple.blogoverflow.com/2012/02/app-update-review-hanging-with-friends/#comment-648826 Sat, 30 Jan 2016 04:26:18 +0000 http://apple.blogoverflow.com/?p=792#comment-648826 I’m having trouble with the same Mission: What’s the Haps?… In it’s description, the mission refers to 2 sections of the game without anything or anywhere describing what is what in the game or so on. Like for example, view the news- didn’t even know the game had news let alone where to find it, bringing me to my next point how am I supposed to know what a drop down is if there isn’t even a Legend explaining what’s what?

]]> Comment on Folder Actions Tutorial: Automation, Meet the Filesystem by Relfi http://apple.blogoverflow.com/2012/06/folder-actions-tutorial-automation-meet-the-filesystem/#comment-646814 Sun, 08 Nov 2015 11:48:03 +0000 http://apple.blogoverflow.com/?p=1527#comment-646814 @Libby I guess you’ve either figured it out by now or forgotten all about it but in case you, or someone else, is still stuck…

sas08 was addressing the issue that you had, i.e. when you rename the screenshot it asks you to rename it again (ad infinitum, or until you hit cancel).

The problem is indeed pretty obvious, if you think about it. * Screencapture app has been changed to save new files to the new folder (e.g. Desktop/Screenshots) * The script is monitoring this Screenshots folder for “new” files (IMPORTANT: it is monitoring for ALL new files that are placed in this folder, not just screenshots) * Your script notices each screenshot (saved by screencapture app, with default name) and asks you to rename the file * The file is then renamed with the filename you supply * Your script then notices this “new” file and prompts you to rename it!

The solution can be as simple as sas08 describes, i.e. add a “Move Finder Items” Action, with the “To:” field set to “Desktop”, to the end of you workflow.

However, I prefer a slightly more complex solution; I agree with the original poster’s recommendation to save screenshots to a separate folder to avoid cluttering the desktop. To make this work follow these steps: * Turn off the Folder Action on the Desktop/Screenshots folder * Create a new subfolder “Desktop/Screenshots/temp” * Edit your Automator workflow to be triggered on this new temp subfolder, rather than the Screenshots folder itself * Add a “Rename Finder Items: Add Date or Time” Action immediately after the “Rename Finder Items: Name Single Item” Action (no need to set/get any more variables, just set the dropdowns as required) * Add a “Move Finder Items” Action with the “To:” field set to “Desktop/Screenshots”

I hope this helps.

]]>
Comment on Allowing iOS 9 and El Capitan questions by Lisa Coffey http://apple.blogoverflow.com/2015/08/beta-ios-9-and-el-capitan-questions-allowed/#comment-646657 Wed, 04 Nov 2015 15:12:09 +0000 http://apple.blogoverflow.com/?p=1718#comment-646657 <

p>I’ve personally done Unit Testing and Acceptance Testing and there is no way I would expose my personal devices to beta software. I don’t have access to the Apple Developers that I would need should a problem arise or would have internally with the organization I was testing for. I would end up dealing with the downtime of my personal production devices, as I do not have test environments that I can work from… on the whole, unless you have spare equipment and a lot of time, public betas or even early adoption of production releases are not the way to go for most users, just look at the deluge of Windows 10 questions on SuperUser. Arguably it is harder for Apple users as OS X and iOS upgrades get pushed to their devices, but even there, waiting a day or two to see if there is an uproar over a glitch can be prudent.

]]>
Comment on App Update Review: Hanging With Friends by Adelta http://apple.blogoverflow.com/2012/02/app-update-review-hanging-with-friends/#comment-643263 Wed, 02 Sep 2015 01:09:14 +0000 http://apple.blogoverflow.com/?p=792#comment-643263 Me too…I can’t find this so called “drop down” to see the news. Can anyone clue us in???

]]> Comment on App Update Review: Hanging With Friends by Adelta http://apple.blogoverflow.com/2012/02/app-update-review-hanging-with-friends/#comment-643261 Wed, 02 Sep 2015 01:05:19 +0000 http://apple.blogoverflow.com/?p=792#comment-643261 The dog is at the bottom of the page in the Zynga logo.

]]> Comment on Blow away, cobwebs by Greg Brown http://apple.blogoverflow.com/2015/06/blow-away-cobwebs/#comment-642823 Thu, 20 Aug 2015 17:08:20 +0000 http://apple.blogoverflow.com/?p=1709#comment-642823 Hi bmike,

I tried to reply earlier but I think I forgot to check the “I’m not a robot” box. You are correct that MarkupKit is a developer tool – I apologize for the confusion.

I would definitely appreciate any suggestions you might have!

Thanks, Greg

]]>
Comment on Allowing iOS 9 and El Capitan questions by bmike http://apple.blogoverflow.com/2015/08/beta-ios-9-and-el-capitan-questions-allowed/#comment-642769 Tue, 18 Aug 2015 22:30:48 +0000 http://apple.blogoverflow.com/?p=1718#comment-642769 Lots of things in your comment, so I’ll gloss over most of it – If you have serious concerns with this change, please air them on meta. Stack Exchange exists to document how things work. Narrow issues are encouraged on all sites as long as the question is adequately documented. We already close questions that are vague – beta or not so documenting that iCloud Photos is buggy in Beta build 5 and not 6 is of great value to have documented publicly IMO even if it lasts for 2 weeks and only helps a dozen people. As to the limited audience, we can review that after we try allowing questions and it seems heavy handed to just rule out legitimate questions on speculation that they won’t get a decent answer. By not entertaining any questions, we guarantee that no one can answer them. I disagree with SO being a place for what we’re allowing – they emphatically do not want OS questions or iTunes Connect questions and actively send them to Ask Different. However, that’s my opinion – if the SO meta gathers enough consensus to adopt iOS 9 beta and OS X beta questions, I certainly would expect we would revisit the scope as a community. Thanks for reading, thanks for commenting.

]]> Comment on Allowing iOS 9 and El Capitan questions by AMR http://apple.blogoverflow.com/2015/08/beta-ios-9-and-el-capitan-questions-allowed/#comment-642706 Mon, 17 Aug 2015 03:53:57 +0000 http://apple.blogoverflow.com/?p=1718#comment-642706 I understand why many may vote up allowing questions on public betas, however, I would have concerns.

I think you are going to end up with many unanswered questions, and many of those questions will continue to get raised over and over as that is how the Community Moderator algorithm bumps up those types of questions, causing future members looking for help to be pushed down the active list.

Answers that are provided will be difficult to peer review as many (most?) active community members will chose to remain of official release software and won’t be able to evaluate the validity and quality of answers given.

That also brings up the fact that if there are fewer community members actually participating in the public beta, then the onus of fielding those questions will fall on a small number of participants. Those participants are likely the more experience members, possibly moderators and developers with a wealth of knowledge on all things Apple, and then Beta questions will take up time that they could be using in the forum answering questions that would benefit from their expertise and would have longer lasting usefulness.

Many questions will likely become irrelevant when the next patch release from Apple is applied. My experience with Stack Exchange is that it tries to have Questions and Answers that remain relevant for long periods of time, and while some might argue that Snow Leopard questions should now be irrelevant, there is still enough of a user base, or even new users who purchase old equipment that can benefit from those answers. The posterity of Beta questions and answers is doubtful beyond a few weeks to months. Does this then mean that Moderator time will then be taken up maintaining the site and purging those questions which no longer have relevance?

Finally, I am of the opinion that public betas should still only be participated in by a small segment of the user population. Many people would not have the expertise to handle problems which can arise from the use of beta software. They may not take the necessary precautions to protect their data. They may end up with substantial service costs to undo the damage if their devices are no longer under AppleCare, if they would even be covered by AppleCare if they chose to install the public beta. You will also get people encouraged to participate who are not providing their feedback to Apple or are providing bad feedback as they do not have the experience with acceptance testing that they need to properly evaluate the bugs that they are seeing and how to document them in a way that developers can benefit from that insight. The more that the Ask Different community fields questions about Public Betas, the more we risk having users who shouldn’t be downloading even RCs jumping on the Public Beta bandwagon, and that could end up being a can of worms that should not be opened, and will likely perpetuate ever more Public Beta questions on Ask Different.

I’ve personally done Unit Testing and Acceptance Testing and there is no way I would expose my personal devices to beta software. I don’t have access to the Apple Developers that I would need should a problem arise or would have internally with the organization I was testing for. I would end up dealing with the downtime of my personal production devices, as I do not have test environments that I can work from… on the whole, unless you have spare equipment and a lot of time, public betas or even early adoption of production releases are not the way to go for most users, just look at the deluge of Windows 10 questions on SuperUser. Arguably it is harder for Apple users as OS X and iOS upgrades get pushed to their devices, but even there, waiting a day or two to see if there is an uproar over a glitch can be prudent.

Possibly there should be an agreement made with StackOverflow to field these questions as there is more of developer community there with more expertise in test software. The other possibility is that an Area 51 proposal for an Apple Developers Stack should be added where Beta questions can either be addressed or moved to if asked on Ask Different. It may also help to split out some of the Swift/XCode questions from StackOverflow and focus the communities in more productive ways.

Does that add up to two cents worth? 🙂

]]>
Comment on Allowing iOS 9 and El Capitan questions by ianc http://apple.blogoverflow.com/2015/08/beta-ios-9-and-el-capitan-questions-allowed/#comment-642570 Thu, 13 Aug 2015 18:46:31 +0000 http://apple.blogoverflow.com/?p=1718#comment-642570 Excellent post and a great example of how the community drives the changes on Stack Exchange sites!

]]>