Page 74 of 90

Re: 43S News

Posted: Wed Mar 25, 2020 10:07 am
by Walter
Nigel (UK) wrote:
Wed Mar 25, 2020 8:46 am
How about SNAP as a name for the key?
Nice idea!

Martin came with SCR.CPY.

Jaco suggested SNIP.

More? (I'd stay away from any labels referring to printing for reasons given above.)

Re: 43S News

Posted: Wed Mar 25, 2020 10:30 am
by Jaymos
Walter wrote:
Wed Mar 25, 2020 10:07 am
Nigel (UK) wrote:
Wed Mar 25, 2020 8:46 am
How about SNAP as a name for the key?
Nice idea!

Martin came with SCR.CPY.

Jaco suggested SNIP.

More? (I'd stay away from any labels referring to printing for reasons given above.)
I listed what the pc companies did and do. I do not particularly like SNIP.

I think you have space for a longer word, options such as SSHOT, SCRSHOT, S.SHOT, SCRNDMP, SNPSHOT, CAPTURE could be considered. I like the option of a camera icon too as per Apple. Personally I prefer the platform standard simultaneous keys.

I don’t think the current SCR.DMP or SCR.CPY are bad with my 52% on SCR.CPY because I dislike Dump.

Re: 43S News

Posted: Wed Mar 25, 2020 1:55 pm
by rprosperi
Among the names suggested so far, I like SSHOT best; I think the period isn't necessary.

And I agree with Jaco that I frequently hit the wrong shift key first, and then when hitting the second shift, would create SSHOT files for no good reason, so I'd prefer a different key location for this command if convenient (probably isn't), however as the flash space is fairly large, this is not a huge concern.

Also, I suggest when this function is executed some brief 'click' sound, or some kind of visual feedback be shown briefly to acknowledge that something has happened, else folks will not be sure anything happened, so hit it again and again, creating multiple files for no reason.

Re: 43S News

Posted: Wed Mar 25, 2020 2:57 pm
by Nigel (UK)
What about a small camera icon, if this is possible?

Nigel (UK)

Re: 43S News

Posted: Wed Mar 25, 2020 3:50 pm
by akaTB
If there's a camera I want it to take photos!

Re: 43S News

Posted: Wed Mar 25, 2020 4:02 pm
by Over_score
Jaymos wrote:
Wed Mar 25, 2020 10:30 am
Personally I prefer the platform standard simultaneous keys.
Me too

Re: 43S News

Posted: Wed Mar 25, 2020 4:11 pm
by Walter
Over_score wrote:
Wed Mar 25, 2020 4:02 pm
Jaymos wrote:
Wed Mar 25, 2020 10:30 am
Personally I prefer the platform standard simultaneous keys.
Me too
Sorry, what? I never used that "platform standard" so far IIRC. Please elaborate a tiny bit.

Re: 43S News

Posted: Wed Mar 25, 2020 4:31 pm
by Jaymos
Walter wrote:
Wed Mar 25, 2020 4:11 pm
Over_score wrote:
Wed Mar 25, 2020 4:02 pm
Jaymos wrote:
Wed Mar 25, 2020 10:30 am
Personally I prefer the platform standard simultaneous keys.
Me too
Sorry, what? I never used that "platform standard" so far IIRC. Please elaborate a tiny bit.
The DM42 platform, i.e. the DMCP program, offers the standard screen capture functionality that we are speaking of now, and it comes decoded already with SHIFT-DISP simultaneous press. This keypress is what you anyway need to capture the system screens as the g[SSHOT] will not work for that.

The point is that you have two sequences on your calculator, whereas the actual DM42-Free42 as well as the DM42-WP43C only has one hidden sequence to capture the screen.
.
Clipboard20.png
Clipboard20.png (14.62 KiB) Viewed 556 times
DM42 System screen capture.
.
Regards
Jaco

Re: 43S News

Posted: Wed Mar 25, 2020 4:58 pm
by Walter
Hidden sequences are not helpful since they are ... ummh ... hidden. And what's SHIFT+DISP on the DM42 (actually SHIFT+E, I assume) may be pure BS on a different layout. Such a trigger for a given functionality must be freely assignable to any other key (or combination of keys) or it's - politely phrased - not wisely designed. Just my opinion.

Re: 43S News

Posted: Wed Mar 25, 2020 8:35 pm
by Stefan Karlsson
Jaymos wrote:
Wed Mar 25, 2020 7:54 am
On both the DM42 hardware and simulator when using WP43S, I frequently find myself in USER mode accidentally, because of a habit of pressing [f] first, incorrectly assuming a function is on f, then pressing [g] after that to correct. Vice versa as well. Now, with SCR.DMP on [f], I expect to have screen dumps accumulating unknowingly.

At least, both items on [f] and [g] double shifts are not stack destructive, but inconvenient only. But then, inconvenience, still, is undesired.

Anybody else have this hard habit to shake?

J
.
Top_ya1.png
I have the same habit (I'm used to the 32 SII).