Comments for Jason Agostoni

Comment on BizTalk Schema Inheritance Practices / Examples by Prasad

Prasad — Fri, 17 Feb 2012 14:13:15 +0000

nice article with good explanation

Comment on iPad: Resize view to account for keyboard (updated) by jagostoni

jagostoni — Fri, 03 Feb 2012 20:38:22 +0000

Thanks, Steve!

Comment on iPad: Resize view to account for keyboard (updated) by Steve Linberg

Steve Linberg — Fri, 03 Feb 2012 19:58:09 +0000

Nice, thank you.

One tweak: I changed the detection logic to make sure that the control’s entire frame is within view, not just its origin point. I had one textfield line up just peeking above the keyboard enough to see the cursor, but not the text

CGRect controlRect = CGRectMake(fieldOrigin.x, fieldOrigin.y, activeField.frame.size.width, activeField.frame.size.height);
if (!CGRectContainsRect(aRect, controlRect) ) {
[controlsScrollView scrollRectToVisible:activeField.frame animated:YES];
}

Comment on BizTalk Schema Inheritance Practices / Examples by Dharm

Dharm — Thu, 19 Jan 2012 10:40:36 +0000

Good explanation. Thank you.

Comment on iPad: Resize view to account for keyboard (updated) by jagostoni

jagostoni — Tue, 03 Jan 2012 16:46:49 +0000

The code I have is integrated with my projects and wouldn’t make sense to post here other than the examples above. When I get a chance, sometime, perhaps I’ll create a demo project and post that.

Comment on iPad: Resize view to account for keyboard (updated) by Oswaldo

Oswaldo — Mon, 02 Jan 2012 21:19:44 +0000

Do you by any chance can post the code for download and analysis?

Comment on iPad: Resize view to account for keyboard (updated) by bjarke

bjarke — Wed, 21 Sep 2011 10:34:10 +0000

Hey Thank you – you saved my day.
I forgot the [self.myScrollView setContentSize:CGSizeMake(768,2000)]; as well which took me an hour to nice – thanks again.

Bjarke
Denmarkl

Comment on New TFS Build Extensions by Community TFS Build Extensions — we’re at it again « Mike Fourie

Sat, 06 Aug 2011 19:04:43 +0000

[...] Shai Raiten, Richard Fennel, Ricci Gian Maria, Willy-Peter Schaub, Jeff Levinson, Leonard Woody, Jason Agostoni, Deepak Gupta, Alvin Ashcraft, Jason [...]

Comment on iPad: Resize view to account for keyboard (updated) by ghr

ghr — Thu, 04 Aug 2011 06:53:34 +0000

Further to the phantom scrolling problem above, I changed the code at the end of the method to the following and it seems to work for me. I realise this may not be optimal but…

if (!CGRectContainsPoint(aRect, fieldOrigin) ) {
//[scrollView scrollRectToVisible:[activeField.superview convertRect:activeField.frame toView:scrollView] //animated:YES];
fieldOrigin = activeField.frame.origin;
fieldOrigin.x = 0.0;
fieldOrigin.y -= 20.0;
[scrollView setContentOffset:fieldOrigin animated:YES];
}

Comment on iPad: Resize view to account for keyboard (updated) by ghr

ghr — Thu, 04 Aug 2011 04:21:53 +0000

Two things to add:
1) Further testing (!) in the above scenario shows that once the hidden field has scrolled to the top of the scrollView and is visible and I start to type, the field then scrolls again off the top of the scrollview so I have to scroll it back down to continue typing!
Not yet sure what’s happening here. The method scrollViewDidScroll is invoked four times by the time the first character is typed – two before and two after.

2) I find that with Anders’ code in place, with my scenario, if I click on any of the fields in the last two rows and then dismiss the keyboard, only the last two rows are displayed at the top of the scrollview – even if I clicked on a field in the last row. It does not return to showing 4 rows.
If I scroll after clicking on any field in the last two rows and then dismiss the keyboard, no scrolling occurs and I am left seeing just those fields visible after I scrolled – which may be what Anders code is trying to achieve. But it has the (unwanted in my view) side effect of not returning to the original starting point if I did not scroll after clicking in a field.