F2 does not select extension

If I use F2 on a selected file, the extension is not included. Is this
new to Win 10? (I've come straight from 15 year with XP.)

Is there a setting or a reliable registry hack I can apply to get back
to what I consider 'normal' operation please?

--
Terry, East Grinstead, UK

Terry Pinnell wrote:
If I use F2 on a selected file, the extension is not included. Is this
new to Win 10? (I've come straight from 15 year with XP.)

Is there a setting or a reliable registry hack I can apply to get back
to what I consider 'normal' operation please?


Apparently the same in Win7. The suggestion is to use
control-a (select all) to extend the selection.

http://answers.microsoft.com/en-us/w...e378b02?auth=1

One participant in the thread claims it is "by design".

Paul

On Thu, 21 Jul 2016 11:52:28 +0100, Terry Pinnell
wrote:

If I use F2 on a selected file, the extension is not included. Is this
new to Win 10? (I've come straight from 15 year with XP.)

Is there a setting or a reliable registry hack I can apply to get back
to what I consider 'normal' operation please?

So far as I know it has been like that since Win 7.

Steve

--
Neural Network Software for Windows http://www.npsnn.com

Stephen Wolstenholme wrote:

Terry Pinnell wrote:

If I use F2 on a selected file, the extension is not included. Is this
new to Win 10? (I've come straight from 15 year with XP.)

So far as I know it has been like that since Win 7.

It has (or rather, if it started with Vista, I wouldn't know anything
about it) I find it more convenient, how often do you want to change the
extension, rather than just the base name?

On Thu, 21 Jul 2016 11:52:28 +0100, Terry Pinnell wrote:

If I use F2 on a selected file, the extension is not included. Is this
new to Win 10? (I've come straight from 15 year with XP.)

Is there a setting or a reliable registry hack I can apply to get back
to what I consider 'normal' operation please?

I've never used it in windows. Just tried it in Linux and it just selects
the filename.Seems to me that is the way it should work, most times the
extension will stay the same.

On 21 Jul 2016, Terry Pinnell wrote in
alt.comp.os.windows-10:

If I use F2 on a selected file, the extension is not included. Is
this new to Win 10? (I've come straight from 15 year with XP.)

I've come to appreciate this feature. Selecting the extension is extra
work, but in the past, NOT selecting the extension was also extra work.
I'd say that more often than not I want to leave the extension intact,
so the new way results in a net savings of effort for me.

Nil wrote:

On 21 Jul 2016, Terry Pinnell wrote in
alt.comp.os.windows-10:

If I use F2 on a selected file, the extension is not included. Is
this new to Win 10? (I've come straight from 15 year with XP.)

I've come to appreciate this feature. Selecting the extension is extra
work, but in the past, NOT selecting the extension was also extra work.
I'd say that more often than not I want to leave the extension intact,
so the new way results in a net savings of effort for me.

Thanks all.

My most frequent use of F2 is within macro scripts (from Macro Express
Pro) which capture a full filename (and path) for later use. I'm
already having to edit hundreds of macros to work in Win 10, for a
variety of other reasons, and this just adds one more. A trivial
change admittedly, but it has to be applied to each individual macro
that includes any F2 commands.

I did try installing a hex editing program to see if I could find a
way to make this sort of change globally. I have a sort of 'composite'
file containing *all* macros, in proprietary format. But the only
changes I've ever been able to make to it are those which retain
exactly the same size. I expect a programmer could do it, but I'm not
one. So the best I can envisage is a macro to step through all my
thousand or so macros and edit those which contain any commands
equivalent to pressing the F2 key.

--
Terry, East Grinstead, UK

Terry Pinnell schreef op 21-07-2016
in :
Nil wrote:

On 21 Jul 2016, Terry Pinnell wrote in
alt.comp.os.windows-10:

If I use F2 on a selected file, the extension is not included. Is
this new to Win 10? (I've come straight from 15 year with XP.)

I've come to appreciate this feature. Selecting the extension is
extra work, but in the past, NOT selecting the extension was also
extra work. I'd say that more often than not I want to leave the
extension intact, so the new way results in a net savings of effort
for me.

Thanks all.

My most frequent use of F2 is within macro scripts (from Macro
Express Pro) which capture a full filename (and path) for later use.
I'm already having to edit hundreds of macros to work in Win 10, for
a variety of other reasons, and this just adds one more. A trivial
change admittedly, but it has to be applied to each individual macro
that includes any F2 commands.

I did try installing a hex editing program to see if I could find a
way to make this sort of change globally. I have a sort of
'composite' file containing *all* macros, in proprietary format. But
the only changes I've ever been able to make to it are those which
retain exactly the same size. I expect a programmer could do it, but
I'm not one. So the best I can envisage is a macro to step through
all my thousand or so macros and edit those which contain any
commands equivalent to pressing the F2 key.

What are you trying to achieve with the macro, which is necessary to
select the extension? Perhaps there is a simple tool for that.

--
MdW.

Machiel de Wit wrote:

Terry Pinnell schreef op 21-07-2016
in :
Nil wrote:

On 21 Jul 2016, Terry Pinnell wrote in
alt.comp.os.windows-10:

If I use F2 on a selected file, the extension is not included. Is
this new to Win 10? (I've come straight from 15 year with XP.)

I've come to appreciate this feature. Selecting the extension is
extra work, but in the past, NOT selecting the extension was also
extra work. I'd say that more often than not I want to leave the
extension intact, so the new way results in a net savings of effort
for me.

Thanks all.

My most frequent use of F2 is within macro scripts (from Macro
Express Pro) which capture a full filename (and path) for later use.
I'm already having to edit hundreds of macros to work in Win 10, for
a variety of other reasons, and this just adds one more. A trivial
change admittedly, but it has to be applied to each individual macro
that includes any F2 commands.

I did try installing a hex editing program to see if I could find a
way to make this sort of change globally. I have a sort of
'composite' file containing *all* macros, in proprietary format. But
the only changes I've ever been able to make to it are those which
retain exactly the same size. I expect a programmer could do it, but
I'm not one. So the best I can envisage is a macro to step through
all my thousand or so macros and edit those which contain any
commands equivalent to pressing the F2 key.

What are you trying to achieve with the macro, which is necessary to
select the extension? Perhaps there is a simple tool for that.

"My most frequent use of F2 is within macro scripts (from Macro
Express
Pro) which capture a full filename (and path) for later use. I'm
already having to edit hundreds of macros to work in Win 10, for a
variety of other reasons, and this just adds one more. A trivial
change admittedly, but it has to be applied to each individual macro
that includes any F2 commands."

'Script'? PLURAL! Many, many different purposes, across scores of
programs.

--
Terry, East Grinstead, UK

Andy Burns wrote:

Stephen Wolstenholme wrote:

Terry Pinnell wrote:

If I use F2 on a selected file, the extension is not included. Is this
new to Win 10? (I've come straight from 15 year with XP.)

So far as I know it has been like that since Win 7.

It has (or rather, if it started with Vista, I wouldn't know anything
about it) I find it more convenient, how often do you want to change the
extension, rather than just the base name?

In fact, if you do change the filetype then you get interrupted with a
popup asking if you really want to change the filetype.

Terry Pinnell wrote:

Nil wrote:

On 21 Jul 2016, Terry Pinnell wrote in
alt.comp.os.windows-10:

If I use F2 on a selected file, the extension is not included. Is
this new to Win 10? (I've come straight from 15 year with XP.)

I've come to appreciate this feature. Selecting the extension is extra
work, but in the past, NOT selecting the extension was also extra work.
I'd say that more often than not I want to leave the extension intact,
so the new way results in a net savings of effort for me.

Thanks all.

My most frequent use of F2 is within macro scripts (from Macro Express
Pro) which capture a full filename (and path) for later use. I'm
already having to edit hundreds of macros to work in Win 10, for a
variety of other reasons, and this just adds one more. A trivial
change admittedly, but it has to be applied to each individual macro
that includes any F2 commands.

I did try installing a hex editing program to see if I could find a
way to make this sort of change globally. I have a sort of 'composite'
file containing *all* macros, in proprietary format. But the only
changes I've ever been able to make to it are those which retain
exactly the same size. I expect a programmer could do it, but I'm not
one. So the best I can envisage is a macro to step through all my
thousand or so macros and edit those which contain any commands
equivalent to pressing the F2 key.

Why not do a global change of "F2" to F2 followed by Ctrl+A" to select
the entire file's name, including extension?

If these same scripts worked under Windows 7 then they should work under
Windows 10. As other have noted, and I concur, F2 only selects the
filename portion. So would it work to select only the filename back in
Windows 7 when you now think you need to include the extension - which
will result in a popup prompt asking if you really want to change the
extension. How did you handle the popup safety prompt?

On Thu, 21 Jul 2016 19:59:19 +0100, Terry Pinnell
wrote:

My most frequent use of F2 is within macro scripts (from Macro Express
Pro) which capture a full filename (and path) for later use. I'm
already having to edit hundreds of macros to work in Win 10, for a
variety of other reasons, and this just adds one more. A trivial
change admittedly, but it has to be applied to each individual macro
that includes any F2 commands.

I did try installing a hex editing program to see if I could find a
way to make this sort of change globally. I have a sort of 'composite'
file containing *all* macros, in proprietary format. But the only
changes I've ever been able to make to it are those which retain
exactly the same size. I expect a programmer could do it, but I'm not
one. So the best I can envisage is a macro to step through all my
thousand or so macros and edit those which contain any commands
equivalent to pressing the F2 key.

I have zero macros, so I probably don't know what I'm missing. In addition
to running a macro to select or change a filename, what are some other
examples of things which you've automated via macros?

Terry Pinnell schreef op 21-07-2016
in :
Machiel de Wit wrote:

Terry Pinnell schreef op 21-07-2016
in :
Nil wrote:

On 21 Jul 2016, Terry Pinnell wrote in
alt.comp.os.windows-10:

If I use F2 on a selected file, the extension is not included. Is
this new to Win 10? (I've come straight from 15 year with XP.)

I've come to appreciate this feature. Selecting the extension is
extra work, but in the past, NOT selecting the extension was also
extra work. I'd say that more often than not I want to leave the
extension intact, so the new way results in a net savings of
effort for me.

Thanks all.

My most frequent use of F2 is within macro scripts (from Macro
Express Pro) which capture a full filename (and path) for later
use. I'm already having to edit hundreds of macros to work in Win
10, for a variety of other reasons, and this just adds one more. A
trivial change admittedly, but it has to be applied to each
individual macro that includes any F2 commands.

I did try installing a hex editing program to see if I could find a
way to make this sort of change globally. I have a sort of
'composite' file containing *all* macros, in proprietary format.
But the only changes I've ever been able to make to it are those
which retain exactly the same size. I expect a programmer could do
it, but I'm not one. So the best I can envisage is a macro to step
through all my thousand or so macros and edit those which contain
any commands equivalent to pressing the F2 key.

What are you trying to achieve with the macro, which is necessary to
select the extension? Perhaps there is a simple tool for that.

"My most frequent use of F2 is within macro scripts (from Macro
Express
Pro) which capture a full filename (and path) for later use. I'm
already having to edit hundreds of macros to work in Win 10, for a
variety of other reasons, and this just adds one more. A trivial
change admittedly, but it has to be applied to each individual macro
that includes any F2 commands."

I can reed, can you reed my question?
"What are you trying to achieve with the macro, which is necessary to
select the extension? Perhaps there is a simple tool for that."

'Script'? PLURAL! Many, many different purposes, across scores of
programs.

So, you won't answer my question. Ik can't help you then.
Contact your software supplier, to enable your wisches.

--
MdW.

Terry Pinnell said :

If I use F2 on a selected file, the extension is not included. Is this
new to Win 10? (I've come straight from 15 year with XP.)

Is there a setting or a reliable registry hack I can apply to get back
to what I consider 'normal' operation please?

It defaults to the file name sans extension.

All you have to do is delete or backspace over the extension in the extremely
rare occasion you should want to change it - for whatever reason.

If you do change the extension or forgetfully delete it, you will still get
the confirmation warning & prompt from Windows 10.

I've considered it an improvement since Windows 7 Pro.

In Terry Pinnell
wrote:

If I use F2 on a selected file, the extension is not included. Is this
new to Win 10? (I've come straight from 15 year with XP.)

Windows 7 Pro works the same way.

--
St. Paul, MN