Re: [MonoTouch] MonoTouch 6 - Package failed to install
The release notes for MT 5.4 tell that it is the last version to support OS X 10.6, so yes, you will have to upgrade. http://docs.xamarin.com/ios/releases/MonoTouch_5/MonoTouch_5.4 On Fri, Sep 28, 2012 at 6:10 AM, stevehatch st...@hatchonline.net wrote: This is a little bit ridicules, I have never had a problem updating monotouch until this update. I know i'm not the only one having problems as there are many posts out there about this install issue. I contacted xamarin support and was told to download the packages directly (not through mono develop) which didn't work any better. No additional response from them. Now they have release 6.0.1, which fails as well. Xamarin- please take this serious and fix it. -- View this message in context: http://monotouch.2284126.n4.nabble.com/MonoTouch-6-Package-failed-to-install-tp4657083p4657301.html Sent from the MonoTouch mailing list archive at Nabble.com. ___ MonoTouch mailing list MonoTouch@lists.ximian.com http://lists.ximian.com/mailman/listinfo/monotouch -- Med Venlig Hilsen / With Best Regards Tomasz Cielecki http://ostebaronen.dk ___ MonoTouch mailing list MonoTouch@lists.ximian.com http://lists.ximian.com/mailman/listinfo/monotouch
Re: [MonoTouch] MonoTouch 6 - Package failed to install
Hi Steve As someone else pointed out: what version of OSX are you running? Nic On Fri, Sep 28, 2012 at 5:10 AM, stevehatch st...@hatchonline.net wrote: This is a little bit ridicules, I have never had a problem updating monotouch until this update. I know i'm not the only one having problems as there are many posts out there about this install issue. I contacted xamarin support and was told to download the packages directly (not through mono develop) which didn't work any better. No additional response from them. Now they have release 6.0.1, which fails as well. Xamarin- please take this serious and fix it. -- View this message in context: http://monotouch.2284126.n4.nabble.com/MonoTouch-6-Package-failed-to-install-tp4657083p4657301.html Sent from the MonoTouch mailing list archive at Nabble.com. ___ MonoTouch mailing list MonoTouch@lists.ximian.com http://lists.ximian.com/mailman/listinfo/monotouch -- Nic Wise t. +44 7788 592 806 | @fastchicken | http://www.linkedin.com/in/nicwise b. http://www.fastchicken.co.nz/ mobileAgent (for FreeAgent): get your accounts in your pocket. http://goo.gl/IuBU Trip Wallet: Keep track of your budget on the go: http://goo.gl/ePhKa Earnest: Self-employed? Track your business expenses and income. http://earnestapp.com Nearest Bus: find when the next bus is coming to your stop. http://goo.gl/Vcz1p London Bike App: Find the nearest Boris Bike, and get riding! http://goo.gl/Icp2 ___ MonoTouch mailing list MonoTouch@lists.ximian.com http://lists.ximian.com/mailman/listinfo/monotouch
Re: [MonoTouch] Fun with MFMailComposeViewController
yeah, I just posted is as an incase, and it's REALLY REALLY not an
obvious bug. If it wasn't for Sebastien's quick thinking, and a bit of
quick debugging at my end, I'd have never found it.
On Fri, Sep 28, 2012 at 3:56 AM, Chris_M kungfuchri...@yahoo.com wrote:
Thanks, Alex! That helps.
Nic, I don't seem to have run afoul of the bug, fortunately. :-)
--Chris
Nic Wise wrote
If you are using MFMailComposeViewController, you may want to look at this
https://bugzilla.xamarin.com/show_bug.cgi?id=7443
Possibly a bug with 6.0.0 / 6.0.1 MT, if you use it in a VERY specific
way when using UIAppearance in a VERY specific way :)
Odds are, you will not hit this, but if you do, it's there :)
On Thu, Sep 27, 2012 at 6:12 AM, Alex White
alexwhite68@
wrote:
Hi Chris,
what works for me is the following two bits of code
pdfFileName = Path.Combine
(Environment.GetFolderPath(Environment.SpecialFolder.MyDocuments),
docs.pdf);
NSData data = NSData.FromFile (pdfFileName);
MFMailComposeViewController mail = new MFMailComposeViewController ();
mail.SetSubject (docs);
mail.SetMessageBody (, true);
mail.Finished += HandleMailFinished;
mail.AddAttachmentData (data, text/x-pdf, docs.pdf);
this.NavigationController.PresentModalViewController (mail, true);
void HandleMailFinished (object sender, MFComposeResultEventArgs e)
{
if (e.Result == MFMailComposeResult.Sent) {
UIAlertView alert = new UIAlertView (sdklsdksdlkskdsd, Mail Sent,
null,
Ok, null);
alert.Show ();
} else if (e.Result == MFMailComposeResult.Cancelled) {
} else if (e.Result == MFMailComposeResult.Saved) {
}
e.Controller.DismissModalViewControllerAnimated (true);
}
you can bung some code in the cancelled result if you need to.
ATB
Alex
On 26 Sep 2012, at 21:28, Chris_M
kungfuchris99@
wrote:
My app has a UITabBarController. One of the tabs is to enable a user to
send
an email to my clients. I created a UIViewController for that tab bar
item,
and in its ViewDidLoad I have code that uses Reachability to determine if
an
internet connection is there, and if
MFMailComposeViewController.CanSendMail, I invoke a MailComposeDelegate
so
the user can compose and send an email. This all works just fine. But I
have
two problems.
First, if I cancel the email composition, and the compose email modal
view
goes away, the view is blank, and navigating away from this screen and
back
to it doesn't reset anything (not that I expected it to). So I need to
figure out how to rest that mail functionality in the
MFMailComposeResult.Cancelled block of code (right now it just disposes
of
the modal view controller in an animated fashion).
Second, when I do send an email, I get a Mail Alert: Mail Sent alert as
expected, but it stays on the screen and effectively locks the app until
I
force close it and launch it again. So obviously I'm missing a step in
there
somewhere. Presumably something I need to add to the
MFMailComposeResult.Sent block of code. Maybe I need to set how many
seconds
the Mail Sent alert stays on the screen, or something like that?
I couldn't find code examples online to help with this, but maybe I'm not
looking for the right things. Anyway, any suggestions?
--Chris
MonoTouch mailing list
MonoTouch@.ximian
http://lists.ximian.com/mailman/listinfo/monotouch
--
View this message in context:
http://monotouch.2284126.n4.nabble.com/Fun-with-MFMailComposeViewController-tp4657247p4657300.html
Sent from the MonoTouch mailing list archive at Nabble.com.
___
MonoTouch mailing list
MonoTouch@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/monotouch
--
Nic Wise
t. +44 7788 592 806 | @fastchicken | http://www.linkedin.com/in/nicwise
b. http://www.fastchicken.co.nz/
mobileAgent (for FreeAgent): get your accounts in your pocket.
http://goo.gl/IuBU
Trip Wallet: Keep track of your budget on the go: http://goo.gl/ePhKa
Earnest: Self-employed? Track your business expenses and income.
http://earnestapp.com
Nearest Bus: find when the next bus is coming to your stop. http://goo.gl/Vcz1p
London Bike App: Find the nearest Boris Bike, and get riding! http://goo.gl/Icp2
___
MonoTouch mailing list
MonoTouch@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/monotouch
Re: [MonoTouch] MonoTouch 6 - Package failed to install
Steve, Can you do the same thing and post your results? -- Can you try the following: sudo /usr/sbin/installer -pkg ~/Library/Caches/XamarinInstaller/MonoTouch/downloads/monotouch-6.0.0.pkg -target / -verboseR and attach the output? Please inform of any dialogs you're shown too. Also, does it help to (re)move your license file (~/Library/MonoTouch/License.v2)? -- Obviously, replace 6.0.0 for 6.0.1 if you have it. Also, as you are on 10.8, can you check in System Preferences - Security and Privacy - General, and see if Gatekeeper is on or not. it's the Allow applcations downloaded from but. It should be AppStore and identified developers or anywhere. Thanks Nic On Fri, Sep 28, 2012 at 1:33 PM, Steve Hatch st...@hatchonline.net wrote: Sorry. 10.8, latest with all updates Sent from my iPhone On Sep 28, 2012, at 4:25 AM, Nic Wise n...@fastchicken.co.nz wrote: Hi Steve As someone else pointed out: what version of OSX are you running? Nic On Fri, Sep 28, 2012 at 5:10 AM, stevehatch st...@hatchonline.net wrote: This is a little bit ridicules, I have never had a problem updating monotouch until this update. I know i'm not the only one having problems as there are many posts out there about this install issue. I contacted xamarin support and was told to download the packages directly (not through mono develop) which didn't work any better. No additional response from them. Now they have release 6.0.1, which fails as well. Xamarin- please take this serious and fix it. -- View this message in context: http://monotouch.2284126.n4.nabble.com/MonoTouch-6-Package-failed-to-install-tp4657083p4657301.html Sent from the MonoTouch mailing list archive at Nabble.com. ___ MonoTouch mailing list MonoTouch@lists.ximian.com http://lists.ximian.com/mailman/listinfo/monotouch -- Nic Wise t. +44 7788 592 806 | @fastchicken | http://www.linkedin.com/in/nicwise b. http://www.fastchicken.co.nz/ mobileAgent (for FreeAgent): get your accounts in your pocket. http://goo.gl/IuBU Trip Wallet: Keep track of your budget on the go: http://goo.gl/ePhKa Earnest: Self-employed? Track your business expenses and income. http://earnestapp.com Nearest Bus: find when the next bus is coming to your stop. http://goo.gl/Vcz1p London Bike App: Find the nearest Boris Bike, and get riding! http://goo.gl/Icp2 -- Nic Wise t. +44 7788 592 806 | @fastchicken | http://www.linkedin.com/in/nicwise b. http://www.fastchicken.co.nz/ mobileAgent (for FreeAgent): get your accounts in your pocket. http://goo.gl/IuBU Trip Wallet: Keep track of your budget on the go: http://goo.gl/ePhKa Earnest: Self-employed? Track your business expenses and income. http://earnestapp.com Nearest Bus: find when the next bus is coming to your stop. http://goo.gl/Vcz1p London Bike App: Find the nearest Boris Bike, and get riding! http://goo.gl/Icp2 ___ MonoTouch mailing list MonoTouch@lists.ximian.com http://lists.ximian.com/mailman/listinfo/monotouch
Re: [MonoTouch] having nightmares with updates to and from xcode
Hi Alex, It's worth investigating. I can make no guarantees that your current hardware is the cause of the xcode syncing problem, of course, but it's possible. Upgrading your hardware certainly wouldn't hurt. A year ago when I was doing a lot of work on the Xcode syncing stuff, I was finding that 4GB of RAM for running 2 copies of MonoDevelop (debugging MonoDevelop inside MonoDevelop) and Xcode side-by-side was a bit on the slow side and once I upgraded my RAM, things ran a lot faster. 8GB of RAM and an SSD should improve things a lot for you. That said, I did find one error in the log files you sent me yesterday indicating a race condition that caused an NRE during one of the last syncs in your most recent MonoDevelop session. I'm not 100% sure that it is the cause of the failure to sync, but it might be. The problem is that I'm not sure how the race was happening (the only way I can see how it could have happened is if our AppleSdkSettings object emitted a Changed event mid-sync, but I'm not sure how that could happen). That was the only code-path that didn't do the proper locking before modifying some internal state variables used by the syncing process. I've added the proper locking for an upcoming MonoDevelop 3.0.4.8 release (I can provide a pre-release download for you as soon as I get to the office). Maybe you can test it out for a few days and see if it seems to solve the issue for you. Hope that helps, Jeff On Fri, Sep 28, 2012 at 3:54 AM, Alex White alexwhit...@gmail.com wrote: Hi Jeff, My issues could come down to the performance of my MacBook it is pretty old a dual core, 4gb of ram, how much better does monodevelop run on a quad core, I see my CPU max'ed out for many minutes at a time when compiling is happening, memory seems to be ok so I am guessing there is not excessive paging of memory, so it comes down to CPU and a bit of hdd. my current MacBook is:- Model Name: MacBook Pro Model Identifier: MacBookPro3,1 Processor Name: Intel Core 2 Duo Processor Speed: 2.2 GHz Number of Processors: 1 Total Number of Cores: 2 L2 Cache: 4 MB Memory: 4 GB Bus Speed: 800 MHz I am contemplating a quad core 15 with a solid state hdd with 8gb of ram, I need to reduce the compile round trip times significantly if I can, is it worth investigating this route? ATB Alex On 27 Sep 2012, at 17:05, Jeff Stedfast j...@xamarin.com wrote: Hi Alex, On Thu, Sep 27, 2012 at 7:24 AM, Alex White alexwhit...@gmail.com wrote: Hi Jeff, thanks for the reply, This problems has been occurring on and off for months, but in the last week 100% of the Xcode updates are no making their way into MonoDevelop it has forced me to recode my project to be xib free, it does not help that this happened right in the middle of a load of work with beta testers, but an xib free app should be better in the long run. I have had so many crashes that always report, some in MonoDevelop and some in Xcode, I have also noted that there are times where the sync'ing back to MonoDevelop has crashed both MonoDevelop and XCode at the same time, both needing to be forced to quit which does not make sense to me as the sync'ing from what I can see is not done via processes but file watching if you see my logic. There's some IPC (via AppleScripting) between MonoDevelop and Xcode as well, during the syncing process, so this might explain that. I will in future use Xcode to only prototype screen layouts then creating the views programatically. Not only do I have to create them from scratch but I cannot use the original names as this throws up so many errors that I cannot fix, I have so many views now with 2's or 3's on the end of them. Also a side issue is renaming of objects in Xcode I have never got this to work properly and be reflected back in MonoDevelop but that is another issue, but having many objects that have the wrong name is not good. Where are the timeouts?, I will have a play with them if they are available to me. Unfortunately, they are not available for users to tweak (they are currently hard-coded in MonoDevelop). MonoDevelop's XcodeSync log file would help me figure out if it is related to the timeouts at all, or if it is something else. I will do some further testing before I go down the route of logging a bug. If you can get your hands on the appropriate XcodeSync log file in the MonoDevelop log directory, that might be enough. I added some fairly verbose debugging WriteLines in MonoDevelop's syncing logic in order to make it easier for me to debug these kinds of issues. You should be able to find them in /Users/name/Library/Logs/MonoDevelop-3.0/Xcode*.log Hope that helps, Jeff ___ MonoTouch mailing list MonoTouch@lists.ximian.com http://lists.ximian.com/mailman/listinfo/monotouch
Re: [MonoTouch] having nightmares with updates to and from xcode
Hi Jeff, Thanks for looking at the logs you have found what I thought you would, race conditions, of course in the perfect world we would have perfect performance so that some of these did not occur, but as with all things programming, if it can go wrong it is only a matter of time before it does. Get me a link to the build and I will have a good go with it, I will still consider the move up to better hardware but in the short term that is not going to happen and it gives us an opportunity to resolve some of these types of issues, what I will do is clear down my Xcode logs once installed then give it a hammering over the next couple of days. Whilst this has been frustrating to say the least, I am really happy with the support I am getting and I am sure we will get to the bottom of things. ATB Alex On 28 Sep 2012, at 15:20, Jeff Stedfast j...@xamarin.com wrote: Hi Alex, It's worth investigating. I can make no guarantees that your current hardware is the cause of the xcode syncing problem, of course, but it's possible. Upgrading your hardware certainly wouldn't hurt. A year ago when I was doing a lot of work on the Xcode syncing stuff, I was finding that 4GB of RAM for running 2 copies of MonoDevelop (debugging MonoDevelop inside MonoDevelop) and Xcode side-by-side was a bit on the slow side and once I upgraded my RAM, things ran a lot faster. 8GB of RAM and an SSD should improve things a lot for you. That said, I did find one error in the log files you sent me yesterday indicating a race condition that caused an NRE during one of the last syncs in your most recent MonoDevelop session. I'm not 100% sure that it is the cause of the failure to sync, but it might be. The problem is that I'm not sure how the race was happening (the only way I can see how it could have happened is if our AppleSdkSettings object emitted a Changed event mid-sync, but I'm not sure how that could happen). That was the only code-path that didn't do the proper locking before modifying some internal state variables used by the syncing process. I've added the proper locking for an upcoming MonoDevelop 3.0.4.8 release (I can provide a pre-release download for you as soon as I get to the office). Maybe you can test it out for a few days and see if it seems to solve the issue for you. Hope that helps, Jeff On Fri, Sep 28, 2012 at 3:54 AM, Alex White alexwhit...@gmail.com wrote: Hi Jeff, My issues could come down to the performance of my MacBook it is pretty old a dual core, 4gb of ram, how much better does monodevelop run on a quad core, I see my CPU max'ed out for many minutes at a time when compiling is happening, memory seems to be ok so I am guessing there is not excessive paging of memory, so it comes down to CPU and a bit of hdd. my current MacBook is:- Model Name: MacBook Pro Model Identifier: MacBookPro3,1 Processor Name: Intel Core 2 Duo Processor Speed:2.2 GHz Number of Processors: 1 Total Number of Cores: 2 L2 Cache: 4 MB Memory: 4 GB Bus Speed: 800 MHz I am contemplating a quad core 15 with a solid state hdd with 8gb of ram, I need to reduce the compile round trip times significantly if I can, is it worth investigating this route? ATB Alex On 27 Sep 2012, at 17:05, Jeff Stedfast j...@xamarin.com wrote: Hi Alex, On Thu, Sep 27, 2012 at 7:24 AM, Alex White alexwhit...@gmail.com wrote: Hi Jeff, thanks for the reply, This problems has been occurring on and off for months, but in the last week 100% of the Xcode updates are no making their way into MonoDevelop it has forced me to recode my project to be xib free, it does not help that this happened right in the middle of a load of work with beta testers, but an xib free app should be better in the long run. I have had so many crashes that always report, some in MonoDevelop and some in Xcode, I have also noted that there are times where the sync'ing back to MonoDevelop has crashed both MonoDevelop and XCode at the same time, both needing to be forced to quit which does not make sense to me as the sync'ing from what I can see is not done via processes but file watching if you see my logic. There's some IPC (via AppleScripting) between MonoDevelop and Xcode as well, during the syncing process, so this might explain that. I will in future use Xcode to only prototype screen layouts then creating the views programatically. Not only do I have to create them from scratch but I cannot use the original names as this throws up so many errors that I cannot fix, I have so many views now with 2's or 3's on the end of them. Also a side issue is renaming of objects in Xcode I have never got this to work properly and be reflected back in MonoDevelop but that is another issue, but having many objects that have the wrong name is not good. Where are the timeouts?, I will have a play with
Re: [MonoTouch] uitableview and uipagecontrol
Hi Adam, Thanks for the reply, I have recoded things and I am much happier with outcome, I was trying to get the scrolling to work in a way that I was happy with but hitting all sorts of issues, mainly with bouncing and the table scrolling out the bounds, this was why I was looking at paging, I solved my issues with a view with a shadow and then the tableview slightly offset the screen looks like I need it to now. ATB Alex ___ MonoTouch mailing list MonoTouch@lists.ximian.com http://lists.ximian.com/mailman/listinfo/monotouch
Re: [MonoTouch] having nightmares with updates to and from xcode
Hi Alex, I've uploaded a pre-release (we haven't bumped the version yet, so it's still called 3.0.4.7): https://files.xamarin.com/~jeff/MonoDevelop-3.0.4.7.dmg Let me know how that works out. Jeff On Fri, Sep 28, 2012 at 10:44 AM, Alex White alexwhit...@gmail.com wrote: Hi Jeff, Thanks for looking at the logs you have found what I thought you would, race conditions, of course in the perfect world we would have perfect performance so that some of these did not occur, but as with all things programming, if it can go wrong it is only a matter of time before it does. Get me a link to the build and I will have a good go with it, I will still consider the move up to better hardware but in the short term that is not going to happen and it gives us an opportunity to resolve some of these types of issues, what I will do is clear down my Xcode logs once installed then give it a hammering over the next couple of days. Whilst this has been frustrating to say the least, I am really happy with the support I am getting and I am sure we will get to the bottom of things. ATB Alex On 28 Sep 2012, at 15:20, Jeff Stedfast j...@xamarin.com wrote: Hi Alex, It's worth investigating. I can make no guarantees that your current hardware is the cause of the xcode syncing problem, of course, but it's possible. Upgrading your hardware certainly wouldn't hurt. A year ago when I was doing a lot of work on the Xcode syncing stuff, I was finding that 4GB of RAM for running 2 copies of MonoDevelop (debugging MonoDevelop inside MonoDevelop) and Xcode side-by-side was a bit on the slow side and once I upgraded my RAM, things ran a lot faster. 8GB of RAM and an SSD should improve things a lot for you. That said, I did find one error in the log files you sent me yesterday indicating a race condition that caused an NRE during one of the last syncs in your most recent MonoDevelop session. I'm not 100% sure that it is the cause of the failure to sync, but it might be. The problem is that I'm not sure how the race was happening (the only way I can see how it could have happened is if our AppleSdkSettings object emitted a Changed event mid-sync, but I'm not sure how that could happen). That was the only code-path that didn't do the proper locking before modifying some internal state variables used by the syncing process. I've added the proper locking for an upcoming MonoDevelop 3.0.4.8 release (I can provide a pre-release download for you as soon as I get to the office). Maybe you can test it out for a few days and see if it seems to solve the issue for you. Hope that helps, Jeff On Fri, Sep 28, 2012 at 3:54 AM, Alex White alexwhit...@gmail.com wrote: Hi Jeff, My issues could come down to the performance of my MacBook it is pretty old a dual core, 4gb of ram, how much better does monodevelop run on a quad core, I see my CPU max'ed out for many minutes at a time when compiling is happening, memory seems to be ok so I am guessing there is not excessive paging of memory, so it comes down to CPU and a bit of hdd. my current MacBook is:- Model Name: MacBook Pro Model Identifier: MacBookPro3,1 Processor Name: Intel Core 2 Duo Processor Speed: 2.2 GHz Number of Processors: 1 Total Number of Cores: 2 L2 Cache: 4 MB Memory: 4 GB Bus Speed: 800 MHz I am contemplating a quad core 15 with a solid state hdd with 8gb of ram, I need to reduce the compile round trip times significantly if I can, is it worth investigating this route? ATB Alex On 27 Sep 2012, at 17:05, Jeff Stedfast j...@xamarin.com wrote: Hi Alex, On Thu, Sep 27, 2012 at 7:24 AM, Alex White alexwhit...@gmail.comwrote: Hi Jeff, thanks for the reply, This problems has been occurring on and off for months, but in the last week 100% of the Xcode updates are no making their way into MonoDevelop it has forced me to recode my project to be xib free, it does not help that this happened right in the middle of a load of work with beta testers, but an xib free app should be better in the long run. I have had so many crashes that always report, some in MonoDevelop and some in Xcode, I have also noted that there are times where the sync'ing back to MonoDevelop has crashed both MonoDevelop and XCode at the same time, both needing to be forced to quit which does not make sense to me as the sync'ing from what I can see is not done via processes but file watching if you see my logic. There's some IPC (via AppleScripting) between MonoDevelop and Xcode as well, during the syncing process, so this might explain that. I will in future use Xcode to only prototype screen layouts then creating the views programatically. Not only do I have to create them from scratch but I cannot use the original names as this throws up so many errors that I cannot fix, I have so many views now with 2's or 3's on the end of them. Also a side issue is renaming of objects in Xcode I have never got this
Re: [MonoTouch] having nightmares with updates to and from xcode
Hi Alex, maybe useless but that's my spec and I have no issues (I'm not yet with MonoTouch 6) and all is done with IB, with more than 30 xibs/forms cross platform with Windows Mobile: Nome do Modelo: MacBook Pro Identificador do Modelo:MacBookPro7,1 Nome do Processador:Intel Core 2 Duo Velocidade do Processador: 2,4 GHz Número de Processadores:1 Número Total de Núcleos:2 Cache de L2:3 MB Memória:8 GB Velocidade do Bus: 1,07 GHz It's something better than what you use but not so better, and the project is small... Memory is high just because I use Fusion with Windows VM and in 1 week it go to almost 0 MB free + Office 2011... My only desired change is to change to a SSD disk (and for the VM, a quadcore... but) Karl Em 28/09/2012, às 11:44, Alex White escreveu: Hi Jeff, Thanks for looking at the logs you have found what I thought you would, race conditions, of course in the perfect world we would have perfect performance so that some of these did not occur, but as with all things programming, if it can go wrong it is only a matter of time before it does. Get me a link to the build and I will have a good go with it, I will still consider the move up to better hardware but in the short term that is not going to happen and it gives us an opportunity to resolve some of these types of issues, what I will do is clear down my Xcode logs once installed then give it a hammering over the next couple of days. Whilst this has been frustrating to say the least, I am really happy with the support I am getting and I am sure we will get to the bottom of things. ATB Alex On 28 Sep 2012, at 15:20, Jeff Stedfast j...@xamarin.com wrote: Hi Alex, It's worth investigating. I can make no guarantees that your current hardware is the cause of the xcode syncing problem, of course, but it's possible. Upgrading your hardware certainly wouldn't hurt. A year ago when I was doing a lot of work on the Xcode syncing stuff, I was finding that 4GB of RAM for running 2 copies of MonoDevelop (debugging MonoDevelop inside MonoDevelop) and Xcode side-by-side was a bit on the slow side and once I upgraded my RAM, things ran a lot faster. 8GB of RAM and an SSD should improve things a lot for you. That said, I did find one error in the log files you sent me yesterday indicating a race condition that caused an NRE during one of the last syncs in your most recent MonoDevelop session. I'm not 100% sure that it is the cause of the failure to sync, but it might be. The problem is that I'm not sure how the race was happening (the only way I can see how it could have happened is if our AppleSdkSettings object emitted a Changed event mid-sync, but I'm not sure how that could happen). That was the only code-path that didn't do the proper locking before modifying some internal state variables used by the syncing process. I've added the proper locking for an upcoming MonoDevelop 3.0.4.8 release (I can provide a pre-release download for you as soon as I get to the office). Maybe you can test it out for a few days and see if it seems to solve the issue for you. Hope that helps, Jeff On Fri, Sep 28, 2012 at 3:54 AM, Alex White alexwhit...@gmail.com wrote: Hi Jeff, My issues could come down to the performance of my MacBook it is pretty old a dual core, 4gb of ram, how much better does monodevelop run on a quad core, I see my CPU max'ed out for many minutes at a time when compiling is happening, memory seems to be ok so I am guessing there is not excessive paging of memory, so it comes down to CPU and a bit of hdd. my current MacBook is:- Model Name:MacBook Pro Model Identifier: MacBookPro3,1 Processor Name:Intel Core 2 Duo Processor Speed: 2.2 GHz Number of Processors: 1 Total Number of Cores: 2 L2 Cache: 4 MB Memory:4 GB Bus Speed: 800 MHz I am contemplating a quad core 15 with a solid state hdd with 8gb of ram, I need to reduce the compile round trip times significantly if I can, is it worth investigating this route? ATB Alex On 27 Sep 2012, at 17:05, Jeff Stedfast j...@xamarin.com wrote: Hi Alex, On Thu, Sep 27, 2012 at 7:24 AM, Alex White alexwhit...@gmail.com wrote: Hi Jeff, thanks for the reply, This problems has been occurring on and off for months, but in the last week 100% of the Xcode updates are no making their way into MonoDevelop it has forced me to recode my project to be xib free, it does not help that this happened right in the middle of a load of work with beta testers, but an xib free app should be better in the long run. I have had so many crashes that always report, some in MonoDevelop and some in Xcode, I have also noted that there are times where the sync'ing back to MonoDevelop has crashed both MonoDevelop and XCode at the same time, both needing to be forced to quit
[MonoTouch] iOS 6 ABAddressBook.RequestAccess example
Hi there,
I'm new to both C# and iOS and I'm looking for an example of how to
implement ABAddressBook.RequestAccess. Here is my code so far:
private bool GetAddressBook ()
{
if (UIDevice.CurrentDevice.CheckSystemVersion (6, 0)) {
NSError err;
iPhoneAddressBook = ABAddressBook.Create (out err);
var authStatus = ABAddressBook.GetAuthorizationStatus();
if (authStatus != ABAuthorizationStatus.Authorized) {
// iPhoneAddressBook.RequestAccess -- is this where to
do it?? how??
using (var alert = new UIAlertView(Contacts
Permission, We need your
permission to access your phone contacts. Please go to Settings Privacy
Contacts, null, OK, null)) {
alert.Show ();
return false;
}
}
return err == null;
} else {
iPhoneAddressBook = new ABAddressBook ();
return true;
}
}
Thanks for your help guys.
--
View this message in context:
http://monotouch.2284126.n4.nabble.com/iOS-6-ABAddressBook-RequestAccess-example-tp4657314.html
Sent from the MonoTouch mailing list archive at Nabble.com.
___
MonoTouch mailing list
MonoTouch@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/monotouch
