Prev: Dynamically change MenuBar Softkey to button or menu
Next: Our QRCodeDecodeSDk supports Windows, PPC and CE
From: Peter Foot on 22 Apr 2008 04:45
GetOpenFileName on Pocket PC/Professional does not fully support
InitialDirectory. It does not accept paths outside of My Documents, and you
can only specify subfolders of My Documents (or I believe first level
folders of a storage card) for example "My Pictures" rather than "\\My
Documents\\My Pictures".

GetOpenFileNameEx on both Smartphone/Standard and Pocket PC/Professional
fully supports any path for the initial directory.

Peter

--
Peter Foot
Microsoft Device Application Development MVP
www.peterfoot.net | www.inthehand.com
In The Hand Ltd - .NET Solutions for Mobility

"The PocketTV Team" <support(a)pockettv.com> wrote in message
news:%23X9wLkCpIHA.3940(a)TK2MSFTNGP03.phx.gbl...
> what do you mean, Peter?
>
> on Pocket PC/Professional edition, GetOpenFileName will take the initial
> directory into account.
>
>> If you use GetOpenFileNameEx directly you can specify an initial
>> directory.
>
> but does it take it into account? because with GetOpenFileName, we can
> also specify an initial directory, and we do that, but it ignores it!
>
> i didn't know that GetOpenFileNameEx had a different behavior, we'll look
> into it. but since lpstrInitialDir can be passed to GetOpenFileName, it
> would seem logical that it takes it into account, just like it does on
> Pocket PC/Professional edition. ideally, also, the file name specified
> should be selected if it exists in the folder specified, must that's
> probably asking for too much :)
>
> backwards compatibility of GetOpenFileName on Smartphone makes little
> sense, since GetOpenFileName was seriously broken (causing application to
> freeze or crash) on Smartphones prior to Windows Mobile 6.1. we tried to
> use it on WM5 and WM6 Smartphones, since we need it, but it was not
> working, so we had to use the tGetFile replacement dll instead.
>
> --
>
> "Peter Foot" <feedback(a)nospam-inthehand.com> wrote in message
> news:E0FBE1F0-D304-43CA-8C9A-F968117231F7(a)microsoft.com...
>>I believe that is for backwards compatibility (this is how GetOpenFileName
>>works on Pocket PC/Professional edition). If you use GetOpenFileNameEx
>>directly you can specify an initial directory.
>>
>> Peter
>>
>> --
>> Peter Foot
>> Microsoft Device Application Development MVP
>> www.peterfoot.net | www.inthehand.com
>> In The Hand Ltd - .NET Solutions for Mobility
>>
>> "The PocketTV Team" <support(a)pockettv.com> wrote in message
>> news:OCowpWPoIHA.4620(a)TK2MSFTNGP06.phx.gbl...
>>> it's a good thing that now GetOpenFileName works on Smartphones (it was
>>> completely broken on Smartphone until WM 6.1).
>>>
>>> however there is an ennoying bug: when lpstrInitialDir is specified in
>>> the OPENFILENAME structure, GetOpenFileName should open the specified
>>> folder.
>>>
>>> on WM 6.1 Smartphones, it seems to open always the "\My Documents"
>>> folder, even when lpstrInitialDir is set to "\Storage Card", for
>>> example.
>>>
>>> this is particularly ennoying when the files to open are located on a
>>> Storage Card. it requires navication by the user, i.e. Menu, select
>>> "Storage Card"...
>>>
>>> Microsoft people (or MVP), please log a bug report on this. we hope this
>>> one will be fixed so that the Smartphone version works as well as the
>>> Pocket PC (WM Professional) version.
>>>
>>> thanks!
>>>
>>
>
>

From: The PocketTV Team on 23 Apr 2008 04:42
"Peter Foot" <feedback(a)nospam-inthehand.com> wrote in message
news:01EE1C30-AC93-4166-A4C0-C01C6617CAAD(a)microsoft.com...
> GetOpenFileName on Pocket PC/Professional does not fully support
> InitialDirectory. It does not accept paths outside of My Documents, and
> you can only specify subfolders of My Documents (or I believe first level
> folders of a storage card) for example "My Pictures" rather than "\\My
> Documents\\My Pictures".

well, yes, it accepts only folders that can be browsed with the
GetOpenFileName dialog, i.e. My Documents or first level of storage card.
and in that case, it does open the right folder upon dialog start-up.

i was just expecting the Smartphone version to do the same :)

> GetOpenFileNameEx on both Smartphone/Standard and Pocket PC/Professional
> fully supports any path for the initial directory.

ok, good to know, thanks for the explanation and clarification!

do you know in what version of Windows Mobile this GetOpenFileNameEx
appeared, and more importantly, in what version of Windows Mobile Standard
this GetOpenFileNameEx works?

i.e. we know that GetOpenFileName is completely broken on Windows Mobile
Standard before 6.1, but is it the same for GetOpenFileNameEx?

-tristan

>
> Peter
>
> --
> Peter Foot
> Microsoft Device Application Development MVP
> www.peterfoot.net | www.inthehand.com
> In The Hand Ltd - .NET Solutions for Mobility
>
> "The PocketTV Team" <support(a)pockettv.com> wrote in message
> news:%23X9wLkCpIHA.3940(a)TK2MSFTNGP03.phx.gbl...
>> what do you mean, Peter?
>>
>> on Pocket PC/Professional edition, GetOpenFileName will take the initial
>> directory into account.
>>
>>> If you use GetOpenFileNameEx directly you can specify an initial
>>> directory.
>>
>> but does it take it into account? because with GetOpenFileName, we can
>> also specify an initial directory, and we do that, but it ignores it!
>>
>> i didn't know that GetOpenFileNameEx had a different behavior, we'll look
>> into it. but since lpstrInitialDir can be passed to GetOpenFileName, it
>> would seem logical that it takes it into account, just like it does on
>> Pocket PC/Professional edition. ideally, also, the file name specified
>> should be selected if it exists in the folder specified, must that's
>> probably asking for too much :)
>>
>> backwards compatibility of GetOpenFileName on Smartphone makes little
>> sense, since GetOpenFileName was seriously broken (causing application to
>> freeze or crash) on Smartphones prior to Windows Mobile 6.1. we tried to
>> use it on WM5 and WM6 Smartphones, since we need it, but it was not
>> working, so we had to use the tGetFile replacement dll instead.
>>
>> --
>>
>> "Peter Foot" <feedback(a)nospam-inthehand.com> wrote in message
>> news:E0FBE1F0-D304-43CA-8C9A-F968117231F7(a)microsoft.com...
>>>I believe that is for backwards compatibility (this is how
>>>GetOpenFileName works on Pocket PC/Professional edition). If you use
>>>GetOpenFileNameEx directly you can specify an initial directory.
>>>
>>> Peter
>>>
>>> --
>>> Peter Foot
>>> Microsoft Device Application Development MVP
>>> www.peterfoot.net | www.inthehand.com
>>> In The Hand Ltd - .NET Solutions for Mobility
>>>
>>> "The PocketTV Team" <support(a)pockettv.com> wrote in message
>>> news:OCowpWPoIHA.4620(a)TK2MSFTNGP06.phx.gbl...
>>>> it's a good thing that now GetOpenFileName works on Smartphones (it was
>>>> completely broken on Smartphone until WM 6.1).
>>>>
>>>> however there is an ennoying bug: when lpstrInitialDir is specified in
>>>> the OPENFILENAME structure, GetOpenFileName should open the specified
>>>> folder.
>>>>
>>>> on WM 6.1 Smartphones, it seems to open always the "\My Documents"
>>>> folder, even when lpstrInitialDir is set to "\Storage Card", for
>>>> example.
>>>>
>>>> this is particularly ennoying when the files to open are located on a
>>>> Storage Card. it requires navication by the user, i.e. Menu, select
>>>> "Storage Card"...
>>>>
>>>> Microsoft people (or MVP), please log a bug report on this. we hope
>>>> this one will be fixed so that the Smartphone version works as well as
>>>> the Pocket PC (WM Professional) version.
>>>>
>>>> thanks!
>>>>
>>>
>>
>>
>


From: Peter Foot on 23 Apr 2008 11:30
GetOpenFileNameEx is implemented in all editions of Windows Mobile 5.0 and
upwards. Prior to 5.0 AKU 2.0 though the details view does not correctly
size the columns and so it is essentially unusable.

Peter

--
Peter Foot
Microsoft Device Application Development MVP
www.peterfoot.net | www.inthehand.com
In The Hand Ltd - .NET Solutions for Mobility

"The PocketTV Team" <support(a)pockettv.com> wrote in message
news:uirzr3RpIHA.2208(a)TK2MSFTNGP04.phx.gbl...
> "Peter Foot" <feedback(a)nospam-inthehand.com> wrote in message
> news:01EE1C30-AC93-4166-A4C0-C01C6617CAAD(a)microsoft.com...
>> GetOpenFileName on Pocket PC/Professional does not fully support
>> InitialDirectory. It does not accept paths outside of My Documents, and
>> you can only specify subfolders of My Documents (or I believe first level
>> folders of a storage card) for example "My Pictures" rather than "\\My
>> Documents\\My Pictures".
>
> well, yes, it accepts only folders that can be browsed with the
> GetOpenFileName dialog, i.e. My Documents or first level of storage card.
> and in that case, it does open the right folder upon dialog start-up.
>
> i was just expecting the Smartphone version to do the same :)
>
>> GetOpenFileNameEx on both Smartphone/Standard and Pocket PC/Professional
>> fully supports any path for the initial directory.
>
> ok, good to know, thanks for the explanation and clarification!
>
> do you know in what version of Windows Mobile this GetOpenFileNameEx
> appeared, and more importantly, in what version of Windows Mobile Standard
> this GetOpenFileNameEx works?
>
> i.e. we know that GetOpenFileName is completely broken on Windows Mobile
> Standard before 6.1, but is it the same for GetOpenFileNameEx?
>
> -tristan
>
>>
>> Peter
>>
>> --
>> Peter Foot
>> Microsoft Device Application Development MVP
>> www.peterfoot.net | www.inthehand.com
>> In The Hand Ltd - .NET Solutions for Mobility
>>
>> "The PocketTV Team" <support(a)pockettv.com> wrote in message
>> news:%23X9wLkCpIHA.3940(a)TK2MSFTNGP03.phx.gbl...
>>> what do you mean, Peter?
>>>
>>> on Pocket PC/Professional edition, GetOpenFileName will take the initial
>>> directory into account.
>>>
>>>> If you use GetOpenFileNameEx directly you can specify an initial
>>>> directory.
>>>
>>> but does it take it into account? because with GetOpenFileName, we can
>>> also specify an initial directory, and we do that, but it ignores it!
>>>
>>> i didn't know that GetOpenFileNameEx had a different behavior, we'll
>>> look into it. but since lpstrInitialDir can be passed to
>>> GetOpenFileName, it would seem logical that it takes it into account,
>>> just like it does on Pocket PC/Professional edition. ideally, also, the
>>> file name specified should be selected if it exists in the folder
>>> specified, must that's probably asking for too much :)
>>>
>>> backwards compatibility of GetOpenFileName on Smartphone makes little
>>> sense, since GetOpenFileName was seriously broken (causing application
>>> to freeze or crash) on Smartphones prior to Windows Mobile 6.1. we tried
>>> to use it on WM5 and WM6 Smartphones, since we need it, but it was not
>>> working, so we had to use the tGetFile replacement dll instead.
>>>
>>> --
>>>
>>> "Peter Foot" <feedback(a)nospam-inthehand.com> wrote in message
>>> news:E0FBE1F0-D304-43CA-8C9A-F968117231F7(a)microsoft.com...
>>>>I believe that is for backwards compatibility (this is how
>>>>GetOpenFileName works on Pocket PC/Professional edition). If you use
>>>>GetOpenFileNameEx directly you can specify an initial directory.
>>>>
>>>> Peter
>>>>
>>>> --
>>>> Peter Foot
>>>> Microsoft Device Application Development MVP
>>>> www.peterfoot.net | www.inthehand.com
>>>> In The Hand Ltd - .NET Solutions for Mobility
>>>>
>>>> "The PocketTV Team" <support(a)pockettv.com> wrote in message
>>>> news:OCowpWPoIHA.4620(a)TK2MSFTNGP06.phx.gbl...
>>>>> it's a good thing that now GetOpenFileName works on Smartphones (it
>>>>> was completely broken on Smartphone until WM 6.1).
>>>>>
>>>>> however there is an ennoying bug: when lpstrInitialDir is specified in
>>>>> the OPENFILENAME structure, GetOpenFileName should open the specified
>>>>> folder.
>>>>>
>>>>> on WM 6.1 Smartphones, it seems to open always the "\My Documents"
>>>>> folder, even when lpstrInitialDir is set to "\Storage Card", for
>>>>> example.
>>>>>
>>>>> this is particularly ennoying when the files to open are located on a
>>>>> Storage Card. it requires navication by the user, i.e. Menu, select
>>>>> "Storage Card"...
>>>>>
>>>>> Microsoft people (or MVP), please log a bug report on this. we hope
>>>>> this one will be fixed so that the Smartphone version works as well as
>>>>> the Pocket PC (WM Professional) version.
>>>>>
>>>>> thanks!
>>>>>
>>>>
>>>
>>>
>>
>
>

From: Rick C on 23 Apr 2008 16:57
"The PocketTV Team" <support(a)pockettv.com> wrote in message
news:uirzr3RpIHA.2208(a)TK2MSFTNGP04.phx.gbl...
> do you know in what version of Windows Mobile this GetOpenFileNameEx
> appeared, and more importantly, in what version of Windows Mobile Standard
> this GetOpenFileNameEx works?
>
> i.e. we know that GetOpenFileName is completely broken on Windows Mobile
> Standard before 6.1, but is it the same for GetOpenFileNameEx?

http://msdn2.microsoft.com/en-us/library/ms854142.aspx says
GetOpenFileNameEx is supported as of WinMo 5 for both PPC and Smartphone.


From: The PocketTV Team on 23 Apr 2008 22:28
thanks!

by any chance, does anyone know the WinCE version and build number that
corresponds to 5.0 AKU 2.0?

-t


"Peter Foot" <feedback(a)nospam-inthehand.com> wrote in message
news:AAC88C1A-7D08-4836-88B9-42E9D6D2A350(a)microsoft.com...
> GetOpenFileNameEx is implemented in all editions of Windows Mobile 5.0 and
> upwards. Prior to 5.0 AKU 2.0 though the details view does not correctly
> size the columns and so it is essentially unusable.
>
> Peter
>
> --
> Peter Foot
> Microsoft Device Application Development MVP
> www.peterfoot.net | www.inthehand.com
> In The Hand Ltd - .NET Solutions for Mobility
>
> "The PocketTV Team" <support(a)pockettv.com> wrote in message
> news:uirzr3RpIHA.2208(a)TK2MSFTNGP04.phx.gbl...
>> "Peter Foot" <feedback(a)nospam-inthehand.com> wrote in message
>> news:01EE1C30-AC93-4166-A4C0-C01C6617CAAD(a)microsoft.com...
>>> GetOpenFileName on Pocket PC/Professional does not fully support
>>> InitialDirectory. It does not accept paths outside of My Documents, and
>>> you can only specify subfolders of My Documents (or I believe first
>>> level folders of a storage card) for example "My Pictures" rather than
>>> "\\My Documents\\My Pictures".
>>
>> well, yes, it accepts only folders that can be browsed with the
>> GetOpenFileName dialog, i.e. My Documents or first level of storage card.
>> and in that case, it does open the right folder upon dialog start-up.
>>
>> i was just expecting the Smartphone version to do the same :)
>>
>>> GetOpenFileNameEx on both Smartphone/Standard and Pocket PC/Professional
>>> fully supports any path for the initial directory.
>>
>> ok, good to know, thanks for the explanation and clarification!
>>
>> do you know in what version of Windows Mobile this GetOpenFileNameEx
>> appeared, and more importantly, in what version of Windows Mobile
>> Standard this GetOpenFileNameEx works?
>>
>> i.e. we know that GetOpenFileName is completely broken on Windows Mobile
>> Standard before 6.1, but is it the same for GetOpenFileNameEx?
>>
>> -tristan
>>
>>>
>>> Peter
>>>
>>> --
>>> Peter Foot
>>> Microsoft Device Application Development MVP
>>> www.peterfoot.net | www.inthehand.com
>>> In The Hand Ltd - .NET Solutions for Mobility
>>>
>>> "The PocketTV Team" <support(a)pockettv.com> wrote in message
>>> news:%23X9wLkCpIHA.3940(a)TK2MSFTNGP03.phx.gbl...
>>>> what do you mean, Peter?
>>>>
>>>> on Pocket PC/Professional edition, GetOpenFileName will take the
>>>> initial directory into account.
>>>>
>>>>> If you use GetOpenFileNameEx directly you can specify an initial
>>>>> directory.
>>>>
>>>> but does it take it into account? because with GetOpenFileName, we can
>>>> also specify an initial directory, and we do that, but it ignores it!
>>>>
>>>> i didn't know that GetOpenFileNameEx had a different behavior, we'll
>>>> look into it. but since lpstrInitialDir can be passed to
>>>> GetOpenFileName, it would seem logical that it takes it into account,
>>>> just like it does on Pocket PC/Professional edition. ideally, also, the
>>>> file name specified should be selected if it exists in the folder
>>>> specified, must that's probably asking for too much :)
>>>>
>>>> backwards compatibility of GetOpenFileName on Smartphone makes little
>>>> sense, since GetOpenFileName was seriously broken (causing application
>>>> to freeze or crash) on Smartphones prior to Windows Mobile 6.1. we
>>>> tried to use it on WM5 and WM6 Smartphones, since we need it, but it
>>>> was not working, so we had to use the tGetFile replacement dll instead.
>>>>
>>>> --
>>>>
>>>> "Peter Foot" <feedback(a)nospam-inthehand.com> wrote in message
>>>> news:E0FBE1F0-D304-43CA-8C9A-F968117231F7(a)microsoft.com...
>>>>>I believe that is for backwards compatibility (this is how
>>>>>GetOpenFileName works on Pocket PC/Professional edition). If you use
>>>>>GetOpenFileNameEx directly you can specify an initial directory.
>>>>>
>>>>> Peter
>>>>>
>>>>> --
>>>>> Peter Foot
>>>>> Microsoft Device Application Development MVP
>>>>> www.peterfoot.net | www.inthehand.com
>>>>> In The Hand Ltd - .NET Solutions for Mobility
>>>>>
>>>>> "The PocketTV Team" <support(a)pockettv.com> wrote in message
>>>>> news:OCowpWPoIHA.4620(a)TK2MSFTNGP06.phx.gbl...
>>>>>> it's a good thing that now GetOpenFileName works on Smartphones (it
>>>>>> was completely broken on Smartphone until WM 6.1).
>>>>>>
>>>>>> however there is an ennoying bug: when lpstrInitialDir is specified
>>>>>> in the OPENFILENAME structure, GetOpenFileName should open the
>>>>>> specified folder.
>>>>>>
>>>>>> on WM 6.1 Smartphones, it seems to open always the "\My Documents"
>>>>>> folder, even when lpstrInitialDir is set to "\Storage Card", for
>>>>>> example.
>>>>>>
>>>>>> this is particularly ennoying when the files to open are located on a
>>>>>> Storage Card. it requires navication by the user, i.e. Menu, select
>>>>>> "Storage Card"...
>>>>>>
>>>>>> Microsoft people (or MVP), please log a bug report on this. we hope
>>>>>> this one will be fixed so that the Smartphone version works as well
>>>>>> as the Pocket PC (WM Professional) version.
>>>>>>
>>>>>> thanks!
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>


First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Dynamically change MenuBar Softkey to button or menu
Next: Our QRCodeDecodeSDk supports Windows, PPC and CE