From: martin rudalics <rudalics@gmx.at>
To: Dmitry Antipov <dmantipov@yandex.ru>, John Wiegley <jwiegley@gmail.com>
Cc: "João Távora" <joaotavora@gmail.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Latest master broken on Cocoa/NS
Date: Fri, 15 Jul 2016 09:28:45 +0200 [thread overview]
Message-ID: <578890AD.3050701@gmx.at> (raw)
In-Reply-To: <676ea8c5-848d-5646-0be4-537fd7c1a1c3@yandex.ru>
> For others, this addresses the cases where tooltips are 'first-class'
> frames in Emacs terms (--with-x-toolkit={no,lucid,motif}, MS Windows,
> GTK[23] builds when 'x-gtk-use-system-tooltips' is nil). The goal was
> to avoid tricky global variables and (hopefully) to reduce overall
> complexity of the relevant code.
Why do we need frame parameters when there can be only one tooltip per
display? Why not put the tooltip timer and the last_show_tip_args into
the display info too just like you did with tip_frame?
martin
next prev parent reply other threads:[~2016-07-15 7:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 21:47 Latest master broken on Cocoa/NS João Távora
2016-07-12 22:05 ` John Wiegley
2016-07-12 22:06 ` João Távora
2016-07-12 22:26 ` John Wiegley
2016-07-14 5:41 ` Dmitry Antipov
2016-07-14 6:26 ` John Wiegley
2016-07-15 6:41 ` Dmitry Antipov
2016-07-15 6:46 ` John Wiegley
2016-07-15 7:25 ` Eli Zaretskii
2016-07-15 7:28 ` martin rudalics [this message]
2016-07-15 8:02 ` Eli Zaretskii
2016-07-15 9:10 ` martin rudalics
2016-07-15 13:35 ` Stefan Monnier
2016-07-15 13:51 ` Clément Pit--Claudel
2016-07-15 14:09 ` Eli Zaretskii
2016-07-15 14:21 ` Clément Pit--Claudel
2016-07-15 14:25 ` Eli Zaretskii
2016-07-15 15:14 ` Clément Pit--Claudel
2016-07-15 16:04 ` Eli Zaretskii
2016-07-15 16:16 ` Clément Pit--Claudel
2016-07-15 17:37 ` Eli Zaretskii
2016-07-15 14:08 ` Dmitry Gutov
2016-07-15 15:20 ` martin rudalics
2016-07-15 16:12 ` Clément Pit--Claudel
2016-07-15 16:41 ` martin rudalics
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=578890AD.3050701@gmx.at \
--to=rudalics@gmx.at \
--cc=dmantipov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=jwiegley@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.