Update on K6TU Remote for iPad Pro and next release

Stu Phillips - K6TU

For those of you with iPad Pro devices, here's a short update.

First the good news; its now clear what I have to do in order to provide full screen support for the iPad Pro. 

With iOS 9 Apple introduced a new way of handling devices with different screen sizes which I did not catch - the development of K6TU Remote started on iOS 8 and its associated XCode tool chain and at that time, there was only one screen size to address.

The not so good news is that the changes needed to have the app run seamlessly on both the regular iPad (the mini has the same screen dimensions) and the Pro are pervasive - for those of your familiar with iOS development, mostly confined to the Storyboard although there are a few places where I will have to adjust for different screen sizes.

There is no bad news!

Its is going to take me some time to readjust the design of all the screen views - I will provide an update as progress is made.  Like most things iOS, the initial learning curve is steep but once climbed, the work is merely repetitious.  Needless to say, the test time is now double as I have to test on both the Air2 and the Pro.

I'm sorry there isn't some magic "one line" fix to this and I appreciate your patience!

I have begun work on a 1.3 which you will see once I’ve re-designed the screen views for the Pro.

This release will add:

• Fix a defect in support for 6300 which precludes using ANT2 as a selection on tx controls
• Support for iPad Pro
• Add Nudge Controls – two directional controls on the screen to allow the frequency to be nudged in step size increments (the step size may or may not be configurable – trying to figure out where to place this)

Needless to say – this has interrupted design and implementation of the CW support!

Still trying to get the work out to the Flex 6000 users beyond those here on the Community - watch for announcements here and on other ham radio related sites as progress on 1.3 nears completion.

73!

Stu K6TU

Al_NN4ZZ

Hi Stu,
Thanks for the update, that sounds good and I'm looking forward to a full screen on the iPad PRO.

I have spent a little time using the iPad PRO on CW.    I usually set the filter to 100HZ.  So the filter is very narrow on the screen.  This make the touch tuning difficult.  Perhaps for CW the filter width displayed on the screen could be done differently.  

• Show the actual filter width  AND

• Show a wider shadow (maybe a different color) for the touch tuning.

Curious if anyone else run into the same issue when trying to touch tune CW....and  what you do.


Regards, Al / NN4ZZ  
al (at) nn4zz (dot) com
6700 - HW......... V 1.5.1.70
SSDR / DAX...... V 1.5.1.152
CAT................... V 1.5.1.0
Win10

Stu Phillips - K6TU

Al,

When tuning for CW, zoom in so that the pan adaptor shows a more drag-able width for the filter window.  Making a wider shadow is a possibility - I will look into it but this will be something for the CW release.

Thanks for the thought.
Stu K6TU

Al_NN4ZZ

Hi Stu,
Yes zooming is a workaround and that is what I'm doing currently.    Thanks for considering the shadow option, I think that would be a good long term fix especially when CW TX is supported and more folks will be using it for CW.

Regards, Al / NN4ZZ  
al (at) nn4zz (dot) com
6700 - HW......... V 1.5.1.70
SSDR / DAX...... V 1.5.1.152
CAT................... V 1.5.1.0
Win10 

Mark_WS7M

Ah iOS development at its best... I created a few apps for the iOS store and successive changes from Apple pretty much killed each one slowly but surely.

Without a doubt I could have recoded or decided to use some new service Apple provided to get around things but none of the apps was making enough to make it worth my time.

I feel your pain Stu.   Not only is new hardware sometimes an issue, sometimes new features provided by iOS make it difficult too.

Mark

W9OY

Not sure how easy it would be to do but maybe create some kind of "snap to" function for CW tuning which would open the bandwidth and automatically set the freq to what ever the offset is, maybe activated by some kind of gesture.  Just an idea.

73  W9OY