unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: 13065@debbugs.gnu.org, duyanning@gmail.com
Subject: bug#13065: Bug in x-file-dialog with GetOpenFileName
Date: Tue, 08 Jan 2013 23:26:20 +0200	[thread overview]
Message-ID: <83r4lvgydf.fsf@gnu.org> (raw)
In-Reply-To: <87pq1fhlbo.fsf@gnu.org>

> From: Jason Rumney <jasonr@gnu.org>
> Cc: Du Yanning <duyanning@gmail.com>,  13065@debbugs.gnu.org
> Date: Tue, 08 Jan 2013 21:10:35 +0800
> 
> 
> Sorry for the late reply.

Thanks for chiming in.

> >  a) Windows 7 deprecated this kind of dialogs and instead wants us to
> >     use some hotshot new ones.  So it could be simply a bug in the
> >     implementation of this dialog on Windows 7.
> 
> Is it not just a case of doing the same as we did previously?
> 
>   /* If we compile with _WIN32_WINNT set to 0x0400 (for NT4
>      compatibility) we end up with the old file dialogs. Define a big
>      enough struct for the new dialog to trick GetOpenFileName into
>      giving us the new dialogs on newer versions of Windows.  */

Sorry, I don't understand: we still do what the above comment
describes.

Thanks for the other info.  Unfortunately, I'm still clueless as to
what could be causing the problem.





  reply	other threads:[~2013-01-08 21:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 11:09 bug#13065: Bug in x-file-dialog with GetOpenFileName Du Yanning
2012-12-04 19:10 ` Eli Zaretskii
2013-01-08 13:10   ` Jason Rumney
2013-01-08 21:26     ` Eli Zaretskii [this message]
2013-01-13 12:52       ` Jason Rumney
2013-01-13 16:35         ` Eli Zaretskii
2013-01-15 18:03           ` Eli Zaretskii
2013-01-16 12:23             ` Jason Rumney
2013-01-16 18:54               ` Eli Zaretskii
2013-01-22 13:32                 ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83r4lvgydf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=13065@debbugs.gnu.org \
    --cc=duyanning@gmail.com \
    --cc=jasonr@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).