R
Richard Plante
Anybody gets problem with the save/load dialog that doesn't show up on
Compact Framework? I am using the standard dialog as shown in the following
example, but the dialog doesn't show up after running for a while in my
application, like it's memory related.
OpenFileDialog fileDialog = new OpenFileDialog();
/* setup dialog... */.
DialogResult dialogResult = fileDialog.ShowDialog();
Please note that I have other windows/dialogs in my application that shows
up properly, whereas the save/load has problems. Is the save/load dialog is
much consuming? Is that dialog is invoking native code underneath or if it's
pure managed code?
The result returned on the call to ShowDialog() is DialogResult.Cancel, no
matter the dialog was not displayed and the user didn't click the cancel
button. Thus, the cancel state is triggered by something else that is not
well documented in Microsoft's documentation.
I would like to figure out the reason of that DialogResult.Cancel state
returned by ShowDialog.
I am using Compact Framework 2.0 SP1 by the way.
....R
Compact Framework? I am using the standard dialog as shown in the following
example, but the dialog doesn't show up after running for a while in my
application, like it's memory related.
OpenFileDialog fileDialog = new OpenFileDialog();
/* setup dialog... */.
DialogResult dialogResult = fileDialog.ShowDialog();
Please note that I have other windows/dialogs in my application that shows
up properly, whereas the save/load has problems. Is the save/load dialog is
much consuming? Is that dialog is invoking native code underneath or if it's
pure managed code?
The result returned on the call to ShowDialog() is DialogResult.Cancel, no
matter the dialog was not displayed and the user didn't click the cancel
button. Thus, the cancel state is triggered by something else that is not
well documented in Microsoft's documentation.
I would like to figure out the reason of that DialogResult.Cancel state
returned by ShowDialog.
I am using Compact Framework 2.0 SP1 by the way.
....R