Display Openfile issue

[Michael Mattias]

That's wrong. The way that the style in question affects the execution of the function is determined by the way that the underlying API function handles that style

I guess we have different views on this subject.

My view:

HOW PowerBASIC Inc chooses to implement the DISPLAY OPENFILE statement is up to PowerBASIC Inc. However, PowerBASIC Inc remains one hundred percent responsible for the documentation and behavior of the DISPLAY OPENFILE statement.

especially when you know that for the most part they are 'wrappers' for API functions
...
The forerunner to 'Display Openfile' was the wrapper 'OpenFileDialog' ...

And you know these things how?

In this particular case your guess would be my guess. I think it is a good guess, but it is only a guess.

Perhaps you have access to PowerBASIC's internal design documentation? News Flash: The rest of us don't.

But even if we did, it does not excuse the fact the observed behavior does not match the documented behavior.

MCM

[Jeff Blakeney]

But even if we did, it does not excuse the fact the observed behavior does not match the documented behavior.

Let's see, the observed behaviour in this case is using %OFN_CREATEPROMPT with DISPLAY OPENFILE does not create a new, empty file. The documentation says this about the %OFN_CREATEPROMPT style:

%OFN_CREATEPROMPT
The user may specify a file which does not exist.

Where is the observed behaviour not matching the documented behaviour? The only thing I could possibly see here is that when using this style, the observed behaviour is that there is a pop up confirmation dialog asking if the user would like to create the file because it doesn't exist and the documentation makes no mention of that being able to happen. Nowhere does the documentation say it will or will not create a new, empty file for you.

I would agree that there should be more in the documentation to explain what happens when using this style but I do not see a conflict between observation and documentation here.

[Michael Mattias]

> the observed behaviour is that there is a pop up confirmation dialog....

No, the observed behaviour is that there is an undocumented pop up confirmation dialog ....

[Jeff Blakeney]

> the observed behaviour is that there is a pop up confirmation dialog....

No, the observed behaviour is that there is an undocumented pop up confirmation dialog ....

Michael, you need to read messages a little more carefully. You just said the same thing I did. Here is the entire sentence I wrote that you quoted part of above (emphasis added):

The only thing I could possibly see here is that when using this style, the observed behaviour is that there is a pop up confirmation dialog asking if the user would like to create the file because it doesn't exist and the documentation makes no mention of that being able to happen.

The confirmation dialog is technically undocumented behaviour but it is standard Windows file dialog behaviour.

[Michael Mattias]

The confirmation dialog is technically undocumented behaviour but it is standard Windows file dialog behaviour

Perhaps we both need to read more carefully.

The confirmation dialog is not "technically" undocumented, it's undocumented.

And so what if a different function - the Windows' function - behaves differently? The Windows' function is not being used here.