www.SwissMicros.com

Right now the sensitivity area is not literally "maximized", I only created a fixed-size border that was kind of half the inter-keys space. It probably sometimes overlaps by a few pixels, and sometimes there is a gap, but overall it should already improve usability :) I'll see in practice if it is w...

Thanks Thomas (again) for your work and help :) I just released a v1.3 that increases the sensitivity border around the keys. This was a problem for using it on the phone, these DM42 keys are quite small and easy to miss with fingers. Let me know if this causes any problem, if so I can either adapt ...

No, the landscape and portrait skin settings are entirely separate. If someone loads the DM42 skin and then selects it for portrait mode, the landscape skin will still be whatever it was before. (Selecting a vertical skin in landscape mode, or selecting a horizontal skin in portrait mode, is possib...

Yes I can provide the gif and layout files directly on github. Maybe it does not make sense to provide a zip for 2 files anyway :) I'm on holidays right now, will do that next week. As far as I understood you have to define one layout for landscape and one layout for portrait. I do not provide any l...

One note: you can achieve the behavior of the DM42 keyboard by mapping the top row to keys 1 through 6, and using direct command mapping for the second row, like so: Key: 101,102 <SensRect> <DispRect> <ActiveLoc> Macro: 101 "Σ+" Macro: 102 "Σ-" Thanks Thomas, I did not knew about this «direct comma...

Hi there :D I have a small gift for you in this holidays season: a DM42 skin for the Free42 simulator: Open source Available in different sizes (up to 2903×5462) The top row can be used to navigate menus, the second row functions are mapped directly and do not require "TOP.FCN", even when a menu is ...

It is maybe not explained in the help file on your calculator, but it is explained in the online official documentation : This item is purely for power OFF testing purposes to avoid time consuming switching between firmwares. It is in no way mentioned to be changed by users. Mode 0 means no deep sle...

Some more data: On battery (Accuracy factor = 0.01): 0..6 = 5.9640E91 (<2 s) 0..13 = 2.7549E951 (<4 s) 0..22 = 1.6059E4621 (<9 s) 0..24 = 2.8145E6000 (<9 s) 0..25 = Out of range On USB (Accuracy factor = 0.01): 0..6 = 5.9640E91 (<1 s) 0..13 = 2.7549E951 (<2 s) 0..22 = 1.6059E4621 (<3 s) 0..24 = 2.81...

:shock: so to save you pressing extra unnecessary buttons, you press extra unnecessary buttons? Nope, I cannot connect the dots here. It's not about pressing unnecessary button, it's about not knowing beforehand if another number or an operand will follow. I think I must just be old-school but reac...

I can't think of a situation where that would be useful. It makes entering numbers on the stack behave more like RPL calculators (apart from the limited stack size). I miss the subtle usefulness of this... :mrgreen: Actually… I find this very useful ! TL;DR: "Exit" allow you to "validate/terminate"...