Page 2 of 3

Re: UPDATE: DMCP-3.14 / DM42-3.14

Posted: Tue Jul 16, 2019 8:44 pm
by revwillie
Pi update applied successfully

Re: UPDATE: DMCP-3.14 / DM42-3.14

Posted: Wed Jul 17, 2019 12:39 am
by rprosperi
HPMike wrote:
Tue Jul 16, 2019 4:37 pm
Can you please re-issue this update with the newest version 2.4.2 of Free42, or do we have to wait another four months to get the latest version of Free42 ?
I'm curious - which features in Free42 2.3.x and 2.4.x are so compelling that a couple hours into this version of DM42 you're looking for the next?

I suppose it must be the new BASE functions as virtually all the other changes are platform-specific and would not apply. If these are important enhancements for you, one suggestion is for you to use Free42 on one of the available platforms that you use to explore and learn these new commands and thus be ready to test and confirm them when they do appear in a new DM42 release.

Re: UPDATE: DMCP-3.14 / DM42-3.14

Posted: Wed Jul 17, 2019 1:30 am
by HPMike
rprosperi wrote:
Wed Jul 17, 2019 12:39 am
HPMike wrote:
Tue Jul 16, 2019 4:37 pm
Can you please re-issue this update with the newest version 2.4.2 of Free42, or do we have to wait another four months to get the latest version of Free42 ?
I'm curious - which features in Free42 2.3.x and 2.4.x are so compelling that a couple hours into this version of DM42 you're looking for the next?

I suppose it must be the new BASE functions as virtually all the other changes are platform-specific and would not apply. If these are important enhancements for you, one suggestion is for you to use Free42 on one of the available platforms that you use to explore and learn these new commands and thus be ready to test and confirm them when they do appear in a new DM42 release.
Not really compelling, I just like having the latest version of Free42 when there's a new DM42 update that's all. Of course I can play with the latest version of Free42 on my iPhone, iPad and Windows PC, and in fact that's exactly what I will do. When I wrote my original post, I was not aware of the complexity of integrating the newer versions of Free42 with the DM42 OS as it is currently formulated, so I'm quite OK with the current state of affairs. :)

Re: UPDATE: DMCP-3.14 / DM42-3.14

Posted: Thu Jul 18, 2019 5:16 am
by Pavel
Thanks for a nice and welcomed upgrade. I have a tiny observation, maybe localized just to my (production) unit: to end the keyboard test I have to use "hard" reset, standard way doesn't work for me.

Re: UPDATE: DMCP-3.14 / DM42-3.14

Posted: Thu Jul 18, 2019 8:48 am
by dlachieze
Thanks for this smooth update. I have one comment regarding the new date format setting: I find it quite confusing.
grsbanks wrote:
Tue Jul 16, 2019 12:19 pm
YMD format

The "SETUP > Settings > Set Date" page had to be altered to allow for the new YMD date format introduced in Free42 2.2.

The first soft menu entry cycles between "M>D>Y", "D>Y>M" and "Y>M>D".

If it shows "M>D>Y" then it means that the current mode is MDY and pressing F1 will make the mode switch to "DMY.

If it shows "D>Y>M" then it means that the current mode is DMY and pressing F1 will make the mode switch to "YMD.

If it shows "Y>M>D" then it means that the current mode is YMD and pressing F1 will make the mode switch to "MDY.
I first thought that there was an error and that D>Y>M should read D>M>Y, then I understood the logic behind it but it doesn’t feel obvious to me.
The reason is that the soft keys "M>D>Y", and "Y>M>D" are matching with the displayed format: MDY or YMD, while "D>Y>M" is not matching with "DMY".
Rather than showing the first letters of the date format cycle, I feel that it would be more intuitive to show the current date format.

So instead of the first soft menu entry cycling between "M>D>Y", "D>Y>M" and "Y>M>D" I would prefer cycling it through "MDY", "DMY" and "YMD".
I don’t think that when you have only 3 options, showing the next one by it’s initial is useful. Just pressing the soft key until you get the date format you need is as simple and effective, and you know in a glance which date format is selected.

Re: UPDATE: DMCP-3.14 / DM42-3.14

Posted: Thu Jul 18, 2019 2:32 pm
by rprosperi
dlachieze wrote:
Thu Jul 18, 2019 8:48 am
So instead of the first soft menu entry cycling between "M>D>Y", "D>Y>M" and "Y>M>D" I would prefer cycling it through "MDY", "DMY" and "YMD".
I don’t think that when you have only 3 options, showing the next one by it’s initial is useful. Just pressing the soft key until you get the date format you need is as simple and effective, and you know in a glance which date format is selected.
Good suggestion. When I checked this new feature, I was looking at the sample date shown in the display as I toggled through the settings, and never caught the button label subtlety. Like you, I get it, but it doesn't feel quite right. Obviously not a priority, but it would be nice to see it adjusted in the future.

@Didier - what would be a good static (i.e. not changing as you press it, to keep the fix easy) label on the button (not easy, and no doubt this is why it is as it is :) )

Re: UPDATE: DMCP-3.14 / DM42-3.14

Posted: Fri Jul 19, 2019 12:25 am
by Dave Britten
I'm noticing some issues with two-key rollover responsiveness in 3.14. For example, try typing 150 really fast, and there's a good chance the 0 will be missed. I don't recall having this issue with 3.13. Anybody else seeing this?

Re: UPDATE: DMCP-3.14 / DM42-3.14

Posted: Fri Jul 19, 2019 10:06 am
by grsbanks
Dave Britten wrote:
Fri Jul 19, 2019 12:25 am
I'm noticing some issues with two-key rollover responsiveness in 3.14. For example, try typing 150 really fast, and there's a good chance the 0 will be missed. I don't recall having this issue with 3.13. Anybody else seeing this?
The reworked keyboard code shouldn't have any effect on that specific scenario. Where the work has gone into is handling repeated presses on the same key, so if you were typing "155" instead and the second "5" was being swallowed, that could conceivably be a result of the new code.

Re: UPDATE: DMCP-3.14 / DM42-3.14

Posted: Fri Jul 19, 2019 11:18 am
by Dave Britten
grsbanks wrote:
Fri Jul 19, 2019 10:06 am
Dave Britten wrote:
Fri Jul 19, 2019 12:25 am
I'm noticing some issues with two-key rollover responsiveness in 3.14. For example, try typing 150 really fast, and there's a good chance the 0 will be missed. I don't recall having this issue with 3.13. Anybody else seeing this?
The reworked keyboard code shouldn't have any effect on that specific scenario. Where the work has gone into is handling repeated presses on the same key, so if you were typing "155" instead and the second "5" was being swallowed, that could conceivably be a result of the new code.
Then there's definitely something peculiar happening. I flashed back to 3.13, and the rollover is fine again.

It seems to only affect some sequences of keys, 5 then 0 being one example. Other sequences were fine, while others would also have a tendency to drop the second keystroke. I'm not sure how the keyboard is wired internally, so perhaps it has to do with whether or not the keys are on the same row/column lines.

Re: UPDATE: DMCP-3.14 / DM42-3.14

Posted: Fri Jul 19, 2019 11:52 am
by Logan
So in my quick testing, it appears that the keyboard does prioritize left to right. So if I am still holding down a 7, 4, 1, 0, I can enter any of the other integers. However, if I hold down say, a 9, 6, 3, then I can't enter 7,8,4,5,1,2,0.

My guess would be that when you're quickly entering a 1,5,0, the 5 is fine because it's to the right of the 1, but the 0 is not because it's to the left of 5 and the 5 probably hasn't released yet.