Opened 15 years ago

Last modified 15 years ago

#1245 closed defect

wxFileSelector with wxOVERWRITE_PROMPT does the wrong thing

Reported by: crazyinsomniac Owned by:
Priority: low Milestone:
Component: Version:
Keywords: Cc: crazyinsomniac, vadz
Blocked By: Blocking:
Patch: no

Description

If you call

wxFileSelector

with the

wxSAVE | wxOVERWRITE_PROMPT

style,
and then you attempt to _save_
a file wich already exists,
you're prompted to overwrite the file (yes or no),
and if you click no,
wxFileSelector returns.

IMHO, that is wrong behaviour.

If a user answers no after being prompted to overwrite,
he should be given a chance to pick
another filename.

Just my 2 cents

Change History (3)

comment:1 Changed 15 years ago by vadz

Which platform is this?

comment:2 Changed 15 years ago by crazyinsomniac

Windows 2000 SP3
wxWindows-2.4.1

I actually stumbled upon this via wxPerl,
but verified it using one of the wxWindows-2.4.1 samples.

Also, it's kind of lame (but not critical)
that this is done in a non-native windows way
(windows file dialogs don't disappear when they prompt you
to overwrite)

comment:3 Changed 15 years ago by vadz

Fixed in 2.5.1. Apparently this was done to work around some
bug with OFN_OVERWRITEPROMPT but I can't reproduce this bug
any more and the emulated behaviour is indeed quite strange
and non native.

Thanks for reoprting!

Note: See TracTickets for help on using tickets.