Third parties may release their own firmware builds and announce them in this forum.
Please note that bugs found in these firmware releases should be posted in this same forum. SwissMicros provides no support for these firmware releases so in the event of a problem, please contact the author of the firmware in question.
When publishing your own build of the DM42 firmware, we require that you include a notice in your "About" screen informing the user that this version of the firmware is neither provided by nor supported by SwissMicros.
I have not checked the forum for a while. The f3 pcm toggle is great, as it now allows for easy debugging of programs with single step and then going back to pcm mode. Thank-you!
I have not checked the forum for a while. The f3 pcm toggle is great, as it now allows for easy debugging of programs with single step and then going back to pcm mode. Thank-you!
Thanks! I‘m actually thinking to make the pcm toggle even easier by making Shift-Custom key press itself a toggle. As a side effect Shift-F3 will become free and It could be assigned to e.g. DM42F3S user function call.
On the another hand, making Shift-Custom toggling pcm would also mean that the original behaviour would not be supported .
I think to assign shift F3 would not be so much benefit as the downside not being 100% compatible with the Original when PCM is of.
If someone needs more functions with F3 then it would already possible now if you start a menu program with DM42F3.
I think the actual version is near the optimum, the only thing that I am not fully convinced is the shift key behavior in PCM because of the three states of the custom menus - I find it less irritating only rotate with up and down instead one time changin to a maybe unwanted line with shift.
I think to assign shift F3 would not be so much benefit as the downside not being 100% compatible with the Original when PCM is of.
If someone needs more functions with F3 then it would already possible now if you start a menu program with DM42F3.
I think the actual version is near the optimum, the only thing that I am not fully convinced is the shift key behavior in PCM because of the three states of the custom menus - I find it less irritating only rotate with up and down instead one time changin to a maybe unwanted line with shift.
Yes, I agree with Peet. I like it the way it is, except for the shift menu. I am happy using the up/down arrows to change the menu. The change of menu with shift is confusing when all I want is a shifted function.
I think to assign shift F3 would not be so much benefit as the downside not being 100% compatible with the Original when PCM is of.
If someone needs more functions with F3 then it would already possible now if you start a menu program with DM42F3.
I think the actual version is near the optimum, the only thing that I am not fully convinced is the shift key behavior in PCM because of the three states of the custom menus - I find it less irritating only rotate with up and down instead one time changing to a maybe unwanted line with shift.
Yes, I agree with Peet. I like it the way it is, except for the shift menu. I am happy using the up/down arrows to change the menu. The change of menu with shift is confusing when all I want is a shifted function.
Thanks for the feedback. I was also not sure if it is a good idea to give up on 100% compatibility when pcm is turned off - convinced - will leave it as it is - means Shift-F3 toggling pcm on and off. Concerning shift that is temporary showing other custom menu - I think this is useful and doesn't really interfere with any other functionality - well, maybe it could be a bit confusing at the beginning but I don't see any other negative effects. At the same time it extends number of easy accessible functions to 12. I will consider adding a configuration option in the setup to turn it on and off.
In the current version (3.19.7) there are only advantages compared to the original firmware and not a single disadvantage.
In this respect, the function of the shift key is not a deal breaker.
The actual shift key performance can offer advantages if you dessign a custom menu matching .... but there is a "but".
... a custom menu has not two BUT three rows.
With normal usage you can reach the next line with the down-arrow (next) and the previous with the up-arrow (back) so there are already 18 easy accessible functions.
Shift does not shift, it rotates (only for the next key pressed) one raw back e.g. from the "01-06 row" to "13-18" or from "13-18" to "07-12" (a little confusing and not easy to explain in a manual). On the other hand, if user uses this as an advantage, the current assignment is of course better for them.
Complemental description: The function of shift in LCLBL is completely confusing. In order to execute XEQ a you do not have to execute XEQ shift A but XEQ shift F
Complemental description: The function of shift in LCLBL is completely confusing. In order to execute XEQ a you do not have to execute XEQ shift A but XEQ shift F
This was indeed very confusing - please test the pre-release version DM42pcm-3.20.8a (shifted pcm is disabled if LCLBL is active - see https://github.com/ljubo106/DM42pcm/releases).