Executive summary: No, there will be no such project for Qt 5.1. And
very likely, for Qt, never.
On 02/13/2013 07:43 AM, Mark wrote:
On Wed, Feb 13, 2013 at 9:49 AM, Knoll Lars lars.kn...@digia.com wrote:
Hi everybody,
I would like to start the feature freeze Qt 5.1 middle of March.
big
On 02/13/2013 12:01 PM, Mark wrote:
On Wed, Feb 13, 2013 at 8:05 PM, Rick Stockton
rickstock...@reno-computerhelp.com wrote:
Executive summary: No, there will be no such project for Qt 5.1. And
very likely, for Qt, never.
On 02/13/2013 07:43 AM, Mark wrote:
On Wed, Feb 13, 2013 at 9:49 AM
On 07/10/2012 07:17 AM, Rick Stockton wrote:
It's awfully late for an API change to Qt5, but this would be an
awkward Backward Compatibility problem to attempt in later Qt5
Releases: Should Qt5 present a 32-bit Button State mask?
Oops, that's WRONG. My initial 32 mouse buttons updates already
It's awfully late for an API change to Qt5, but this would be an awkward
Backward Compatibility problem to attempt in later Qt5 Releases: Should
Qt5 present a 32-bit Button State mask?
** Background **
As you all remember, I added more mouse buttons for MouseButtonPress
and
Please excuse the Top-Post, my suggestion is VERY short:
The terminology Optional Dependency sounds like a good term for these
situations. (At least to me, a native 'en-us' person.)
On 05/08/2012 06:18 AM, David Jarvie wrote:
On Tue, May 8, 2012 1:07 pm, Allen Winter wrote:
On Tuesday 08 May
The main text of my reply is at the bottom ...
On 04/16/2012 05:15 AM, Michael Jansen wrote:
On Sunday, April 15, 2012 08:40:38 PM Thiago Macieira wrote:
On segunda-feira, 16 de abril de 2012 01.33.31, Stephen Kelly wrote:
The only applications that should do that are the workspace fixture
, schrieb Rick Stockton
rickstock...@reno-computerhelp.com:
I disagree. Things such as Window Position, Size, and the need to
Move a Window (to expose a UI keyboard) may also be fundamental for
Applications on Handheld Platforms (as being described in another ...
GTK seems to agree with me; all
Partly in reply to Albert Astals Cid and Thomas Zander, on the KDE list
(December 26):
I am aware of the timing requirement (But Thomas- thanks for the
reminder, in case I HADN'T been.) Since I'm the person who will write
the code and doco, I HAVE TO have an idea how to make it work ;) I've
Thomas, Todd, and Albert: this is pointed at you guys for suggestions.
Thiago, it's mostly FYI at this point. Final design and subsequent
coding in Qt, starting in about a week.
I have created a Qt Devnet forum Thread for work on Mouse Shortcuts.
It's at
It is time for us to Fish, or Cut Byte on two alternative ways to
introduce Mouse-Oriented Shortcuts into Qt5 and KDE-Next:
Todd RME has been suggesting a new design- oriented around DBUS.
Unfortunately, I don't know how to do that coding. Todd, if your design
gets a more favorable review
I need advice- do the masters of KDE consider
https://bugs.kde.org/show_bug.cgi?id=48062 to be important?
It's got a ton of votes, but I'll SWAG that a majority opf those votes
were really votes for https://bugs.kde.org/show_bug.cgi?id=96431 -- get
higher-numbered mouse buttons into the
My thanks to you, MGrasslin, Aaron, Todd rme, and Thiago for
coaching me towards this achievement. The new code is small, and
VERY simple. We have no API changes (at least, not yet--- we should
implement a mouse button mask "getter" as a new feature, but that's
for later
A kde-core post as well, because I'm offering to resurrect the Dead. ;)
Looking ahead, it's going to be awkward mixing Qt names for Buttons =
XButton2, while using X11 names for higher numbers. I'm new to C++, but
pretty solid on everything except polymorphism and certain asepcts of
I've been inspired by the 'shortcut doc' Thread on kwin ML. This
concerns mouse devices with extra buttons driving our desktop, and
creating mouse-based shortcuts.
SAD STORY
You may recall that, many months ago, I was encouraged to try a Qt
enhancement for this. Qt consumes X11 ButtonPress
In reply to Allen Winter (and Hugo, and Aaron):
I feel that Allen's idea/suggestion is really good -- having MYSELF made
the mistake of 'poking around' in the master branch for a while. If it
had been completely empty of files, I'd have gotten a really big clue
instantly.
BTW, Will a '4.8'
This is inspired by Todd RME's post in Vol 99, Issue 83. Todd's post in
kde-core-devel refers to the original bug number, QTBUG-16092, but that
bug is so riddled with unworkable baggage that I cloned another. The
real work will be in QTBUG-19238. QTBUG-19238 currently contains
start-up work on
PREAMBLE:
Hi. I'm the X11-oriented mouse guy whom Todd mentioned in his last
call for GSOC, what about shortcuts? post (Topic #1 in Vol 95, Issue 69).
His focus is within KDE itself, while I'm focusing from the lower
layers, moving up into KDE Development tools, API, and UI from those
lower
17 matches
Mail list logo
