Hope for 42s in iOS 11?

[kristia...@gmail.com]

Is there any hope for an updated version of 42s RPN Calculator, so it will still run when iOS 11 arrives?

I would gladly pay for an updated version.

K

[John Kono]

We've been waiting for an update since the iPhone 5(!) came out, so I wouldn't hold my breath...

John

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

[kristia...@gmail.com]

Yes, so have I. But so far it's just been an inconvenience. With iOS 11 it's game over without an update.

[John Kono]

All too true, sadly. I held out hope until the 6 came out, but finally had to give in and switch over to Free42 and WP34s. I've still got it installed on my 7+, but it just looks... sad.

John

> On Jun 7, 2017, at 23:40, kristia...@gmail.com wrote:
>
> Yes, so have I. But so far it's just been an inconvenience. With iOS 11 it's game over without an update.
>

[kristia...@gmail.com]

I don't mind so much the lack of 5+ screen height. It would of course be nice if it did stretch all the way and maybe added more stack rows, but just a rebuild of the current version to make it work in iOS 11 would be perfectly fine by me.

[Byron Foster]

So I submitted a new release, it's in review now.   It's been compiled with the latest Xcode.  It won't run on any iOS version earlier than 8.0 since Xcode doesn't support any prior versions.  It looks like crap on any screen other then the now ancient 3.5 inch display.  Any continued development on the app will drop the bit map keyboard and will use a generated keypad using native graphics so that it can stretch and accommodate the many varieties of display sizes.  sorry about the the more than late update. I suck!  I hope this goes smoothly... there are allot of changes in the build and submission process. 

[John Kono]

Sweet!  Thanks for the update, and it's good to know that you're still around and the app is still alive. :)

John

On Jun 12, 2017, at 00:13, Byron Foster <by...@base2.cc> wrote:

So I submitted a new release, it's in review now.   It's been compiled with the latest Xcode.  It won't run on any iOS version earlier than 8.0 since Xcode doesn't support any prior versions.  It looks like crap on any screen other then the now ancient 3.5 inch display.  Any continued development on the app will drop the bit map keyboard and will use a generated keypad using native graphics so that it can stretch and accommodate the many varieties of display sizes.  sorry about the the more than late update. I suck!  I hope this goes smoothly... there are allot of changes in the build and submission process. 

--

[kristia...@gmail.com]

Byron: you totally don't suck! :-) You're the creator of the best calculator app on iOS. Although the new updated version requires an acquired taste due to the screen size issue, I for sure will continue to use it, and cross fingers that you find time to complete the refactoring for new dynamic UI fitting various screens.

Thank you for keeping a good app alive.

K

[Filippo Forlani]

I am with you: this is the best calculator app on iOS!
(and sometimes I wonder what could be developing features not in 42s, like graphs and some simple programming features, not only for better input... :D )

[tom...@gmail.com]

Thanks for the update Byron. Native keyboard would be fine by me. I can imagine the difficulty for one developer to support the large range of screen sizes now available.

[Byron Foster]

I wonder if anyone would care if I dropped support for the 3.5 inch display.  iOS has!

[kristia...@gmail.com]

I would think dropping support for 3.5" is ok.

[thoma...@gmail.com]

"It won't run on any iOS version earlier than 8.0 since Xcode doesn't support any prior versions."

Is that because you're using newer APIs? Because if not, you can target as far back as 6.0. Free42 still runs on 6.0 and it's built with the latest Xcode.

(Of course that may change if I ever redo the UI with the more recent dynamic layout features...)

[thoma...@gmail.com]

"I would think dropping support for 3.5" is ok."

I know a few people who still use iPhone 4 or 4S. iPod touch users tend to be even less interested in upgrading. I've even had people ask about bringing back iOS 3.1.3 support as recently as last year. :-O

[thoma...@gmail.com]

Regarding support for larger screens: I've found that once I added 4" support in Free42, requests for large screen support have practically stopped. It's probably because the larger screens all have the same aspect ratio, so the 4" skin fills the screen nicely even on the 6, 6+, etc., and the scaling is so smooth it's barely noticeable.

[Byron Foster]

I know a few people who still use iPhone 4 or 4S. iPod touch users tend to be even less interested in upgrading. I've even had people ask about bringing back iOS 3.1.3 support as recently as last year. :-O

Hey Thomas!

iOS 3.1.3??? Really! Yea, I still have my 4S which I like very much, but I use it as an iPod now.  

On Thursday, June 22, 2017 at 6:52:29 PM UTC-7, thoma...@gmail.com wrote:

Regarding support for larger screens: I've found that once I added 4" support in Free42, requests for large screen support have practically stopped. It's probably because the larger screens all have the same aspect ratio, so the 4" skin fills the screen nicely even on the 6, 6+, etc., and the scaling is so smooth it's barely noticeable.

I have an alpha version of a larger screen now, It really just pushes the keyboard down and has a larger LCD by default.   If I support the 3.5 inch display, which sounds like I probably should, It will probably loose some functionality,  mainly the ability to slide the top row of keys down to make the LCD larger.  I thought it was kinda slick functionality on the old 3.5 inch display iPhones, but it really doesn't make since anymore with the larger screens, and I don't want to support it for a of niche device now.  

I also have an alpha version of a keyboard using native graphics that I worked on a few years ago and I brushed off  the dust lately.  I hit a snag though trying to support some of the graphics I needed to make it look similar to the authentic 42s keyboard.  

Ultimately the last big feature I always wanted to add but never got to it was the ability to customize the top keys.  I think this functionality flows naturally from Free42s CUSTOM feature.  I would probably just add a couple more menu levels to CUSTOM and project those onto the keys.   

[Byron Foster]

No, I'm not using any new APIs.  In fact, allot of time was spent fixing all the deprecated API calls, thanks to Jeff for helping out with this!  I was assuming that the deployment target setting in Xcode was the minimum deployment version, but I may likely be mistaken.  The earliest target allowed was 8.0 with the latest Xcode. 

[thoma...@gmail.com]

Hey Byron,

Sounds like you have some cool stuff coming up. Can't wait to see it!

Regarding the deployment target: I think you have to edit the pbxproj file manually to set it lower than 8.0. And 6.0 seems to be a hard limit for some reason; I tried setting it to 4.3, but that didn't work.

[mick....@mac.com]

I too can't wait for a version of 42s on my iPhone 6s that shows the full calculator buttons AND the expanded LCD. I don't suppose you have a progress update...

Also, if you're collecting votes, I'd be perfectly fine abandoning all support for the 3.5" screen

Finally, would it be possible to replace the LCD pixellated font with a much easier to read normal fixed width font. I expect that's more difficult to implement than it seems though. 

[abu...@gmail.com]

Not sure I need a calculator scaling up to fill the screen of my iPad Pro - what if that extra real estate displayed both the printout and calculator side by side?
That would be really useful - incl. the ability to copy and paste from the tape.