Hi guys!
working i refresh all the available patches of qt3 and qt3 trinity patches... now there's no "hunks"..
BUT: i need info about it! theres some patches that repeat! and re-defines a coupe of functions! i filter some one but i wnat to fix all existences of issues and fixeds from any project, currently i have the trinity patches, ARCH patches, Debian patches, some from WinBuntu and i not found SUSE and if there any others please send me please!
i any found the info about every/any patch please report but with link info.. merge unkown patches its not segure!
inside patche stheres info (only some) about fixed, but no links povided, and qt nokia bug traker not have history on qt3 complete fixeds o open bugs!
On Mon, May 9, 2011 at 08:46, PICCORO McKAY Lenz mckaygerhard@gmail.com wrote:
Hi guys!
working i refresh all the available patches of qt3 and qt3 trinity patches... now there's no "hunks"..
Why? There's only one patch of qt3 3.3.8b. And I just remade it too.
BUT: i need info about it! theres some patches that repeat! and re-defines a coupe of functions! i filter some one but i wnat to fix all existences of issues and fixeds from any project, currently i have the trinity patches, ARCH patches, Debian patches, some from WinBuntu and i not found SUSE and if there any others please send me please!
I wouldn't recommend that, most distributions have abandoned qt3 and it's better because those are probably distro-specific patches. There are always reasons.
Le Mon, 9 May 2011 11:09:52 -0400, Robert Xu robxu9@gmail.com a écrit :
On Mon, May 9, 2011 at 08:46, PICCORO McKAY Lenz mckaygerhard@gmail.com wrote:
Hi guys!
working i refresh all the available patches of qt3 and qt3 trinity patches... now there's no "hunks"..
Why? There's only one patch of qt3 3.3.8b. And I just remade it too.
BUT: i need info about it! theres some patches that repeat! and re-defines a coupe of functions! i filter some one but i wnat to fix all existences of issues and fixeds from any project, currently i have the trinity patches, ARCH patches, Debian patches, some from WinBuntu and i not found SUSE and if there any others please send me please!
I wouldn't recommend that, most distributions have abandoned qt3 and it's better because those are probably distro-specific patches. There are always reasons.
There are also the qt-copy patches, which originate from KDE developers. See http://websvn.kde.org/branches/qt/3.3/qt-copy/patches/ .
Thanks Xu, all the KDE patches are refresh now..
theres still qt3specific fixeds patches, some from trinity (taken from over net ) and i hear theres more on SUSE, where i found these? also a coupe of info about the currently at KDE, trinity and qt3 specific fixeds?
there currenly aroud: 39 KDE/qt-bugs patcheds for fixeds : all refresh now! 40 debian contribution fixeds : all upo to date 2 trinity ajust patches (qt3 3.3.8c) 4 trinity-arch contribution fixeds patches
the complete documentation its also buildin, i search for info about these all qt3 specific patches (the 40 KDE/qt-bugs fixeds contribution), if SUSE have some one please send me info about it!
On 5/9/11, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
Le Mon, 9 May 2011 11:09:52 -0400, Robert Xu robxu9@gmail.com a écrit :
On Mon, May 9, 2011 at 08:46, PICCORO McKAY Lenz mckaygerhard@gmail.com wrote:
Hi guys!
working i refresh all the available patches of qt3 and qt3 trinity patches... now there's no "hunks"..
Why? There's only one patch of qt3 3.3.8b. And I just remade it too.
BUT: i need info about it! theres some patches that repeat! and re-defines a coupe of functions! i filter some one but i wnat to fix all existences of issues and fixeds from any project, currently i have the trinity patches, ARCH patches, Debian patches, some from WinBuntu and i not found SUSE and if there any others please send me please!
I wouldn't recommend that, most distributions have abandoned qt3 and it's better because those are probably distro-specific patches. There are always reasons.
There are also the qt-copy patches, which originate from KDE developers. See http://websvn.kde.org/branches/qt/3.3/qt-copy/patches/ .
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Mon, May 9, 2011 at 11:43, PICCORO McKAY Lenz mckaygerhard@gmail.com wrote:
Thanks Xu, all the KDE patches are refresh now..
theres still qt3specific fixeds patches, some from trinity (taken from over net ) and i hear theres more on SUSE, where i found these? also a coupe of info about the currently at KDE, trinity and qt3 specific fixeds?
there currenly aroud: 39 KDE/qt-bugs patcheds for fixeds : all refresh now! 40 debian contribution fixeds : all upo to date 2 trinity ajust patches (qt3 3.3.8c)
*2*? There is only one AFAIK.
4 trinity-arch contribution fixeds patches
the complete documentation its also buildin, i search for info about these all qt3 specific patches (the 40 KDE/qt-bugs fixeds contribution), if SUSE have some one please send me info about it!
See for yourself. build.opensuse.org, project KDE:KDE3, package qt3.
2 trinity ajust patches (qt3 3.3.8c)
*2*? There is only one AFAIK.
2: 1) the improvements for trinity destop, but theres no raise verwsion up ! 2) a extra patch for raise version to 3.3.8b to 3.3.8c, ARCH patches has both in one patch
Thanks for links, now searching....
On Mon, May 9, 2011 at 14:10, PICCORO McKAY Lenz mckaygerhard@gmail.com wrote:
2 trinity ajust patches (qt3 3.3.8c)
*2*? There is only one AFAIK.
2: 1) the improvements for trinity destop, but theres no raise verwsion up !
Yes there is.
On 05/09/2011 07:46 AM, PICCORO McKAY Lenz wrote:
Hi guys!
working i refresh all the available patches of qt3 and qt3 trinity patches... now there's no "hunks"..
BUT: i need info about it! theres some patches that repeat! and re-defines a coupe of functions! i filter some one but i wnat to fix all existences of issues and fixeds from any project, currently i have the trinity patches, ARCH patches, Debian patches, some from WinBuntu and i not found SUSE and if there any others please send me please!
i any found the info about every/any patch please report but with link info.. merge unkown patches its not segure!
inside patche stheres info (only some) about fixed, but no links povided, and qt nokia bug traker not have history on qt3 complete fixeds o open bugs!
I don't know if it helps, but on Arch Linux, you can look at all the patches I'm applying here:
http://www.3111skyline.com/dl/dt/trinity/arch/pbpkg/trinity-qt3/
(the PKGBUILD file is just the Arch build script, the rest are patches)
These patches have had a recent look by Baho. He removed some of the outdated patches. I'm not sure if there are others that could be helpful --or-- if there are some I'm using that I should get rid of. Right now things are working well with the Qt3 Arch package.
Let me know if I can help.
http://www.3111skyline.com/dl/dt/trinity/arch/pbpkg/trinity-qt3/
(the PKGBUILD file is just the Arch build script, the rest are patches)
I have revised and refresh all, thanks , excelent work at kde3 portage on ARCH
Let me know if I can help.
Thanks, now i'm research at links provide by Xu
O.o excelente resource!!!!
https://build.opensuse.org/project/packages?project=KDE:KDE3
^_^ thanks
On 5/9/11, PICCORO McKAY Lenz mckaygerhard@gmail.com wrote:
http://www.3111skyline.com/dl/dt/trinity/arch/pbpkg/trinity-qt3/
(the PKGBUILD file is just the Arch build script, the rest are patches)
I have revised and refresh all, thanks , excelent work at kde3 portage on ARCH
Let me know if I can help.
Thanks, now i'm research at links provide by Xu
Le Mon, 09 May 2011 13:10:38 -0500, "David C. Rankin" drankinatty@suddenlinkmail.com a écrit :
On 05/09/2011 07:46 AM, PICCORO McKAY Lenz wrote:
Hi guys!
working i refresh all the available patches of qt3 and qt3 trinity patches... now there's no "hunks"..
BUT: i need info about it! theres some patches that repeat! and re-defines a coupe of functions! i filter some one but i wnat to fix all existences of issues and fixeds from any project, currently i have the trinity patches, ARCH patches, Debian patches, some from WinBuntu and i not found SUSE and if there any others please send me please!
i any found the info about every/any patch please report but with link info.. merge unkown patches its not segure!
inside patche stheres info (only some) about fixed, but no links povided, and qt nokia bug traker not have history on qt3 complete fixeds o open bugs!
I don't know if it helps, but on Arch Linux, you can look at all the patches I'm applying here:
http://www.3111skyline.com/dl/dt/trinity/arch/pbpkg/trinity-qt3/
(the PKGBUILD file is just the Arch build script, the rest are patches)
These patches have had a recent look by Baho. He removed some of the outdated patches. I'm not sure if there are others that could be helpful --or-- if there are some I'm using that I should get rid of. Right now things are working well with the Qt3 Arch package.
Are the qt-copy patches from KDE3 outdated ? I am using them on Slackware64 and they are used on the trinity-qt3 and qt3-trinity PKGBUILDs from AUR (with some exceptions, because I patch qt-3.3.8b instead of qt-3.3.8). To Tim and Serghei: I am currently building Trinity SVN (with TQt3) on Slackware64 13.37, with KDE4 installed alongside, and have some patches to dbus-tqt and kdebase that enable building on Slackware64 13.37 with default options. I will publish them once I have a really working kdebase/kdelibs (now I have a lot of "missing *.la" style errors when I start Trinity on Xephyr).
Let me know if I can help.
On Mon, May 9, 2011 at 14:28, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
These patches have had a recent look by Baho. He removed some of the outdated patches. I'm not sure if there are others that could be helpful --or-- if there are some I'm using that I should get rid of. Right now things are working well with the Qt3 Arch package.
Are the qt-copy patches from KDE3 outdated ? I am using them on Slackware64 and they are used on the trinity-qt3 and qt3-trinity PKGBUILDs from AUR (with some exceptions, because I patch qt-3.3.8b instead of qt-3.3.8). To Tim and Serghei: I am currently building Trinity SVN (with TQt3) on Slackware64 13.37, with KDE4 installed alongside, and have some patches to dbus-tqt and kdebase that enable building on Slackware64 13.37 with default options. I will publish them once I have a really working kdebase/kdelibs (now I have a lot of "missing *.la" style errors when I start Trinity on Xephyr).
I think SuSE is still maintaining qt3.
i confir still mantain qt3, a member of this list made a last commit ---> Ilya Chernykh anixxsus@gmail.com (i think )
The KDE patches , some are outdated, but not all, i revise all, !
Please /dev/ammo42 could u deatil me these pactches?, and of course, some kde patches on qt3 are old, die 3.3.8b fixeds some...
On 5/9/11, Robert Xu robxu9@gmail.com wrote:
On Mon, May 9, 2011 at 14:28, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
These patches have had a recent look by Baho. He removed some of the outdated patches. I'm not sure if there are others that could be helpful --or-- if there are some I'm using that I should get rid of. Right now things are working well with the Qt3 Arch package.
Are the qt-copy patches from KDE3 outdated ? I am using them on Slackware64 and they are used on the trinity-qt3 and qt3-trinity PKGBUILDs from AUR (with some exceptions, because I patch qt-3.3.8b instead of qt-3.3.8). To Tim and Serghei: I am currently building Trinity SVN (with TQt3) on Slackware64 13.37, with KDE4 installed alongside, and have some patches to dbus-tqt and kdebase that enable building on Slackware64 13.37 with default options. I will publish them once I have a really working kdebase/kdelibs (now I have a lot of "missing *.la" style errors when I start Trinity on Xephyr).
I think SuSE is still maintaining qt3.
-- later, Robert Xu
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Le Mon, 9 May 2011 14:38:14 -0430, PICCORO McKAY Lenz mckaygerhard@gmail.com a écrit :
i confir still mantain qt3, a member of this list made a last commit ---> Ilya Chernykh anixxsus@gmail.com (i think )
The KDE patches , some are outdated, but not all, i revise all, !
Please /dev/ammo42 could u deatil me these pactches?, and of course, some kde patches on qt3 are old, die 3.3.8b fixeds some...
I took the patches here: http://aur.archlinux.org/packages.php?ID=46631 and removed the patches that don't apply because they are already in qt-3.3.8b. Here is an attachment containing: -the Slackware-13.0 unsupported SlackBuild and some related files (I slightly modified the SlackBuild) -the Slackware-specific patches, already present in Slackware 12.2 which included KDE 3.5.10 (they are the compressed ones) -the patches from MutantTurkey's PKGBUILD, without the ones included in qt-3.3.8b.
On 5/9/11, Robert Xu robxu9@gmail.com wrote:
On Mon, May 9, 2011 at 14:28, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
These patches have had a recent look by Baho. He removed some of the outdated patches. I'm not sure if there are others that could be helpful --or-- if there are some I'm using that I should get rid of. Right now things are working well with the Qt3 Arch package.
Are the qt-copy patches from KDE3 outdated ? I am using them on Slackware64 and they are used on the trinity-qt3 and qt3-trinity PKGBUILDs from AUR (with some exceptions, because I patch qt-3.3.8b instead of qt-3.3.8). To Tim and Serghei: I am currently building Trinity SVN (with TQt3) on Slackware64 13.37, with KDE4 installed alongside, and have some patches to dbus-tqt and kdebase that enable building on Slackware64 13.37 with default options. I will publish them once I have a really working kdebase/kdelibs (now I have a lot of "missing *.la" style errors when I start Trinity on Xephyr).
I think SuSE is still maintaining qt3.
-- later, Robert Xu
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
please help:
About the 67101 and 101516 (these dublicated of fisrt) The old qt-copy patch #0032 seems was wrong, and the real problem is in the X server as can i see ttps://bugs.freedesktop.org/show_bug.cgi?id=2965 .
I should remove this patch, any body removed from ARCH or slak builds?
On 5/9/11, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
Le Mon, 9 May 2011 14:38:14 -0430, PICCORO McKAY Lenz mckaygerhard@gmail.com a écrit :
i confir still mantain qt3, a member of this list made a last commit ---> Ilya Chernykh anixxsus@gmail.com (i think )
The KDE patches , some are outdated, but not all, i revise all, !
Please /dev/ammo42 could u deatil me these pactches?, and of course, some kde patches on qt3 are old, die 3.3.8b fixeds some...
I took the patches here: http://aur.archlinux.org/packages.php?ID=46631 and removed the patches that don't apply because they are already in qt-3.3.8b. Here is an attachment containing: -the Slackware-13.0 unsupported SlackBuild and some related files (I slightly modified the SlackBuild) -the Slackware-specific patches, already present in Slackware 12.2 which included KDE 3.5.10 (they are the compressed ones) -the patches from MutantTurkey's PKGBUILD, without the ones included in qt-3.3.8b.
On 5/9/11, Robert Xu robxu9@gmail.com wrote:
On Mon, May 9, 2011 at 14:28, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
These patches have had a recent look by Baho. He removed some of the outdated patches. I'm not sure if there are others that could be helpful --or-- if there are some I'm using that I should get rid of. Right now things are working well with the Qt3 Arch package.
Are the qt-copy patches from KDE3 outdated ? I am using them on Slackware64 and they are used on the trinity-qt3 and qt3-trinity PKGBUILDs from AUR (with some exceptions, because I patch qt-3.3.8b instead of qt-3.3.8). To Tim and Serghei: I am currently building Trinity SVN (with TQt3) on Slackware64 13.37, with KDE4 installed alongside, and have some patches to dbus-tqt and kdebase that enable building on Slackware64 13.37 with default options. I will publish them once I have a really working kdebase/kdelibs (now I have a lot of "missing *.la" style errors when I start Trinity on Xephyr).
I think SuSE is still maintaining qt3.
-- later, Robert Xu
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Le Tue, 10 May 2011 14:31:00 -0430, PICCORO McKAY Lenz mckaygerhard@gmail.com a écrit :
please help:
About the 67101 and 101516 (these dublicated of fisrt) The old qt-copy patch #0032 seems was wrong, and the real problem is in the X server as can i see ttps://bugs.freedesktop.org/show_bug.cgi?id=2965 .
Effectively, it seems to be a kludge. From man Xrandr:
The XRRScreenChangeNotify event is sent to clients that ask to be informed whenever the root window configuration changes. Configuration changes may include resolution, physical size, subpixel order (see XRender(3)), and rotation. Note that changes to any or all of these could occur due to external events (user control in the X server, a different monitor/flat panel display being hot-plugged) and is not only the result of a protocol/library request to the X server.
I should remove this patch, any body removed from ARCH or slak builds?
I just removed it. Anyway, like every other qt-copy patch, it has never been included in Slackware, and it didn't prevent Slackware's KDE3 from working well. Keeping it would not introduce bugs, but just perhaps slow the library (but I don't think it would slow it much).
<snip>
theres a refresh workaround .. i consult htat reverification of notifi Xrand , i applied that for comp backguard on minimal builds:
This patch replaces the old #0032 patch as actually just a workaround. Taken from debian builds:
--- a/src/kernel/qapplication_x11.cpp +++ b/src/kernel/qapplication_x11.cpp @@ -3407,7 +3407,8 @@ int QApplication::x11ProcessEvent( XEven #endif
#ifndef QT_NO_XRANDR - if (event->type == xrandr_eventbase + RRScreenChangeNotify) { + if (event->type == xrandr_eventbase + RRScreenChangeNotify + || ( event->type == ConfigureNotify && event->xconfigure.window == QPaintDevice::x11AppRootWindow())) { // update Xlib internals with the latest screen configuration XRRUpdateConfiguration(event)
On 5/10/11, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
Le Tue, 10 May 2011 14:31:00 -0430, PICCORO McKAY Lenz mckaygerhard@gmail.com a écrit :
please help:
About the 67101 and 101516 (these dublicated of fisrt) The old qt-copy patch #0032 seems was wrong, and the real problem is in the X server as can i see ttps://bugs.freedesktop.org/show_bug.cgi?id=2965 .
Effectively, it seems to be a kludge. From man Xrandr:
The XRRScreenChangeNotify event is sent to clients that ask to be informed whenever the root window configuration changes. Configuration changes may include resolution, physical size, subpixel order (see XRender(3)), and rotation. Note that changes to any or all of these could occur due to external events (user control in the X server, a different monitor/flat panel display being hot-plugged) and is not only the result of a protocol/library request to the X server.
I should remove this patch, any body removed from ARCH or slak builds?
I just removed it. Anyway, like every other qt-copy patch, it has never been included in Slackware, and it didn't prevent Slackware's KDE3 from working well. Keeping it would not introduce bugs, but just perhaps slow the library (but I don't think it would slow it much).
<snip>
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Le Tue, 10 May 2011 15:11:51 -0430, PICCORO McKAY Lenz mckaygerhard@gmail.com a écrit :
theres a refresh workaround .. i consult htat reverification of notifi Xrand , i applied that for comp backguard on minimal builds:
This patch replaces the old #0032 patch as actually just a workaround. Taken from debian builds:
--- a/src/kernel/qapplication_x11.cpp +++ b/src/kernel/qapplication_x11.cpp @@ -3407,7 +3407,8 @@ int QApplication::x11ProcessEvent( XEven #endif
#ifndef QT_NO_XRANDR
- if (event->type == xrandr_eventbase + RRScreenChangeNotify) {
- if (event->type == xrandr_eventbase + RRScreenChangeNotify
- || ( event->type == ConfigureNotify &&
event->xconfigure.window == QPaintDevice::x11AppRootWindow())) { // update Xlib internals with the latest screen configuration XRRUpdateConfiguration(event)
It's exactly the same patch.
On 5/10/11, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
Le Tue, 10 May 2011 14:31:00 -0430, PICCORO McKAY Lenz mckaygerhard@gmail.com a écrit :
please help:
About the 67101 and 101516 (these dublicated of fisrt) The old qt-copy patch #0032 seems was wrong, and the real problem is in the X server as can i see ttps://bugs.freedesktop.org/show_bug.cgi?id=2965 .
Effectively, it seems to be a kludge. From man Xrandr:
The XRRScreenChangeNotify event is sent to clients that ask to be informed whenever the root window configuration changes. Configuration changes may include resolution, physical size, subpixel order (see XRender(3)), and rotation. Note that changes to any or all of these could occur due to external events (user control in the X server, a different monitor/flat panel display being hot-plugged) and is not only the result of a protocol/library request to the X server.
I should remove this patch, any body removed from ARCH or slak builds?
I just removed it. Anyway, like every other qt-copy patch, it has never been included in Slackware, and it didn't prevent Slackware's KDE3 from working well. Keeping it would not introduce bugs, but just perhaps slow the library (but I don't think it would slow it much).
<snip>
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
¬_¬u
On 5/10/11, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
Le Tue, 10 May 2011 15:11:51 -0430, PICCORO McKAY Lenz mckaygerhard@gmail.com a écrit :
theres a refresh workaround .. i consult htat reverification of notifi Xrand , i applied that for comp backguard on minimal builds:
This patch replaces the old #0032 patch as actually just a workaround. Taken from debian builds:
--- a/src/kernel/qapplication_x11.cpp +++ b/src/kernel/qapplication_x11.cpp @@ -3407,7 +3407,8 @@ int QApplication::x11ProcessEvent( XEven #endif
#ifndef QT_NO_XRANDR
- if (event->type == xrandr_eventbase + RRScreenChangeNotify) {
- if (event->type == xrandr_eventbase + RRScreenChangeNotify
- || ( event->type == ConfigureNotify &&
event->xconfigure.window == QPaintDevice::x11AppRootWindow())) { // update Xlib internals with the latest screen configuration XRRUpdateConfiguration(event)
It's exactly the same patch.
On 5/10/11, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
Le Tue, 10 May 2011 14:31:00 -0430, PICCORO McKAY Lenz mckaygerhard@gmail.com a écrit :
please help:
About the 67101 and 101516 (these dublicated of fisrt) The old qt-copy patch #0032 seems was wrong, and the real problem is in the X server as can i see ttps://bugs.freedesktop.org/show_bug.cgi?id=2965 .
Effectively, it seems to be a kludge. From man Xrandr:
The XRRScreenChangeNotify event is sent to clients that ask to be informed whenever the root window configuration changes. Configuration changes may include resolution, physical size, subpixel order (see XRender(3)), and rotation. Note that changes to any or all of these could occur due to external events (user control in the X server, a different monitor/flat panel display being hot-plugged) and is not only the result of a protocol/library request to the X server.
I should remove this patch, any body removed from ARCH or slak builds?
I just removed it. Anyway, like every other qt-copy patch, it has never been included in Slackware, and it didn't prevent Slackware's KDE3 from working well. Keeping it would not introduce bugs, but just perhaps slow the library (but I don't think it would slow it much).
<snip>
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
from slack patchs, the two patchs: qt-x11.diff.gz qt.x86.cflags.diff.gz
Must no aplliet due the "qt-x11.diff.gz" its configured at configure time with -qt-gif parameter and the "qt.x86.cflags.diff" only apllied to x86 archs.
On Tue, May 10, 2011 at 3:18 PM, PICCORO McKAY Lenz mckaygerhard@gmail.comwrote:
¬_¬u
On 5/10/11, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
Le Tue, 10 May 2011 15:11:51 -0430, PICCORO McKAY Lenz mckaygerhard@gmail.com a écrit :
theres a refresh workaround .. i consult htat reverification of notifi Xrand , i applied that for comp backguard on minimal builds:
This patch replaces the old #0032 patch as actually just a workaround. Taken from debian builds:
--- a/src/kernel/qapplication_x11.cpp +++ b/src/kernel/qapplication_x11.cpp @@ -3407,7 +3407,8 @@ int QApplication::x11ProcessEvent( XEven #endif
#ifndef QT_NO_XRANDR
- if (event->type == xrandr_eventbase + RRScreenChangeNotify) {
- if (event->type == xrandr_eventbase + RRScreenChangeNotify
- || ( event->type == ConfigureNotify &&
event->xconfigure.window == QPaintDevice::x11AppRootWindow())) { // update Xlib internals with the latest screen configuration XRRUpdateConfiguration(event)
It's exactly the same patch.
On 5/10/11, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
Le Tue, 10 May 2011 14:31:00 -0430, PICCORO McKAY Lenz mckaygerhard@gmail.com a écrit :
please help:
About the 67101 and 101516 (these dublicated of fisrt) The old qt-copy patch #0032 seems was wrong, and the real problem is in the X server as can i see ttps://bugs.freedesktop.org/show_bug.cgi?id=2965 .
Effectively, it seems to be a kludge. From man Xrandr:
The XRRScreenChangeNotify event is sent to clients that ask to be informed whenever the root window configuration changes. Configuration changes may include resolution, physical size, subpixel order (see XRender(3)), and rotation. Note that changes to any or all of these could occur due to external events (user control in the X server, a different monitor/flat panel display being hot-plugged) and is not only the result of a protocol/library request to the X server.
I should remove this patch, any body removed from ARCH or slak builds?
I just removed it. Anyway, like every other qt-copy patch, it has never been included in Slackware, and it didn't prevent Slackware's KDE3 from working well. Keeping it would not introduce bugs, but just perhaps slow the library (but I don't think it would slow it much).
<snip>
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
To unsubscribe, e-mail:
trinity-devel-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com Cofundador de Venenux; debian based multimedia alike free only zealots users (oh well, i try but..too many free guidelines buahhh) http://shutendouji.net creador de massenkoh linux; debian enhanchements for better up to date support on stable brand, including non-free soft.
Le Wed, 11 May 2011 11:25:27 -0430, PICCORO McKAY Lenz mckaygerhard@gmail.com a écrit :
from slack patchs, the two patchs: qt-x11.diff.gz qt.x86.cflags.diff.gz
Must no aplliet due the "qt-x11.diff.gz" its configured at configure time with -qt-gif parameter and the "qt.x86.cflags.diff" only apllied to x86 archs.
Anyway, Slackware-specific patches are usually not interesting because since Slackware patches software as little as possible, the patches end up being trivial. There are some exceptions: for example, polkit on Slackware 13.1 was heavily patched to avoid having PAM in the distribution (in 13.37 the patch seems to be merged in upstream), and xfig comes with a lot of ancient, but still present, patches (some of these are from February 2004).
On Tue, May 10, 2011 at 3:18 PM, PICCORO McKAY Lenz mckaygerhard@gmail.comwrote:
¬_¬u
On 5/10/11, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
Le Tue, 10 May 2011 15:11:51 -0430, PICCORO McKAY Lenz mckaygerhard@gmail.com a écrit :
theres a refresh workaround .. i consult htat reverification of notifi Xrand , i applied that for comp backguard on minimal builds:
This patch replaces the old #0032 patch as actually just a workaround. Taken from debian builds:
--- a/src/kernel/qapplication_x11.cpp +++ b/src/kernel/qapplication_x11.cpp @@ -3407,7 +3407,8 @@ int QApplication::x11ProcessEvent( XEven #endif
#ifndef QT_NO_XRANDR
- if (event->type == xrandr_eventbase + RRScreenChangeNotify)
{
- if (event->type == xrandr_eventbase + RRScreenChangeNotify
- || ( event->type == ConfigureNotify &&
event->xconfigure.window == QPaintDevice::x11AppRootWindow())) { // update Xlib internals with the latest screen configuration XRRUpdateConfiguration(event)
It's exactly the same patch.
On 5/10/11, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
Le Tue, 10 May 2011 14:31:00 -0430, PICCORO McKAY Lenz mckaygerhard@gmail.com a écrit :
please help:
About the 67101 and 101516 (these dublicated of fisrt) The old qt-copy patch #0032 seems was wrong, and the real problem is in the X server as can i see ttps://bugs.freedesktop.org/show_bug.cgi?id=2965 .
Effectively, it seems to be a kludge. From man Xrandr:
The XRRScreenChangeNotify event is sent to clients that ask to be informed whenever the root window configuration changes. Configuration changes may include resolution, physical size, subpixel order (see XRender(3)), and rotation. Note that changes to any or all of these could occur due to external events (user control in the X server, a different monitor/flat panel display being hot-plugged) and is not only the result of a protocol/library request to the X server.
I should remove this patch, any body removed from ARCH or slak builds?
I just removed it. Anyway, like every other qt-copy patch, it has never been included in Slackware, and it didn't prevent Slackware's KDE3 from working well. Keeping it would not introduce bugs, but just perhaps slow the library (but I don't think it would slow it much).
<snip>
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
To unsubscribe, e-mail:
trinity-devel-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com Cofundador de Venenux; debian based multimedia alike free only zealots users (oh well, i try but..too many free guidelines buahhh) http://shutendouji.net creador de massenkoh linux; debian enhanchements for better up to date support on stable brand, including non-free soft.
I have that in mind, I am currently focused on SUSE patchs, the most interesting, since the url that i have https://build.opensuse.org/project/packages?project=KDE:KDE3 are the only who v' ones who remain active to minor maintenance qt3 libraries and others kde3 related projects/soft
in fes hours i release a tarball in shutendouji.net
On Wed, May 11, 2011 at 1:42 PM, /dev/ammo42 mickeytintincolle@yahoo.frwrote:
Le Wed, 11 May 2011 11:25:27 -0430, PICCORO McKAY Lenz mckaygerhard@gmail.com a écrit :
from slack patchs, the two patchs: qt-x11.diff.gz qt.x86.cflags.diff.gz
Must no aplliet due the "qt-x11.diff.gz" its configured at configure time with -qt-gif parameter and the "qt.x86.cflags.diff" only apllied to x86 archs.
Anyway, Slackware-specific patches are usually not interesting because since Slackware patches software as little as possible, the patches end up being trivial. There are some exceptions: for example, polkit on Slackware 13.1 was heavily patched to avoid having PAM in the distribution (in 13.37 the patch seems to be merged in upstream), and xfig comes with a lot of ancient, but still present, patches (some of these are from February 2004).
On Tue, May 10, 2011 at 3:18 PM, PICCORO McKAY Lenz mckaygerhard@gmail.comwrote:
¬_¬u
On 5/10/11, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
Le Tue, 10 May 2011 15:11:51 -0430, PICCORO McKAY Lenz mckaygerhard@gmail.com a écrit :
theres a refresh workaround .. i consult htat reverification of notifi Xrand , i applied that for comp backguard on minimal builds:
This patch replaces the old #0032 patch as actually just a workaround. Taken from debian builds:
--- a/src/kernel/qapplication_x11.cpp +++ b/src/kernel/qapplication_x11.cpp @@ -3407,7 +3407,8 @@ int QApplication::x11ProcessEvent( XEven #endif
#ifndef QT_NO_XRANDR
- if (event->type == xrandr_eventbase + RRScreenChangeNotify)
{
- if (event->type == xrandr_eventbase + RRScreenChangeNotify
- || ( event->type == ConfigureNotify &&
event->xconfigure.window == QPaintDevice::x11AppRootWindow())) { // update Xlib internals with the latest screen configuration XRRUpdateConfiguration(event)
It's exactly the same patch.
On 5/10/11, /dev/ammo42 mickeytintincolle@yahoo.fr wrote:
Le Tue, 10 May 2011 14:31:00 -0430, PICCORO McKAY Lenz mckaygerhard@gmail.com a écrit :
> please help: > > About the 67101 and 101516 (these dublicated of fisrt) The old > qt-copy patch #0032 seems was wrong, and the real problem is > in the X server as can i see > ttps://bugs.freedesktop.org/show_bug.cgi?id=2965 . Effectively, it seems to be a kludge. From man Xrandr: >The XRRScreenChangeNotify event is sent to clients that >ask to be informed whenever the root window configuration >changes. Configuration changes may include resolution, >physical size, subpixel order (see XRender(3)), and rotation. >Note that changes to any or all of these could occur due to >external events (user control in the X server, a different >monitor/flat panel display being hot-plugged) and is not only >the result of a protocol/library request to the X server.
> > I should remove this patch, any body removed from ARCH or slak > builds? I just removed it. Anyway, like every other qt-copy patch, it has never been included in Slackware, and it didn't prevent Slackware's KDE3 from working well. Keeping it would not introduce bugs, but just perhaps slow the library (but I don't think it would slow it much). > <snip>
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
To unsubscribe, e-mail:
trinity-devel-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com Cofundador de Venenux; debian based multimedia alike free only zealots users (oh well, i try but..too many free guidelines buahhh) http://shutendouji.net creador de massenkoh linux; debian enhanchements for better up to date support on stable brand, including non-free soft.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Wed, May 11, 2011 at 14:37, PICCORO McKAY Lenz mckaygerhard@gmail.com wrote:
I have that in mind, I am currently focused on SUSE patchs, the most interesting, since the url that i have https://build.opensuse.org/project/packages?project=KDE:KDE3%C2%A0are%C2%A0t... only who v' ones who remain active to minor maintenance qt3 libraries and others kde3 related projects/soft in fes hours i release a tarball in shutendouji.net
*PLEASE don't use HTML email! It completely screws up my email client*
Why a tarball? We are all merging it to SVN (hopefully).
i dont have a real machine, i connect from a cyber cafe, in live cd, also i dont have 24/7 conections.. i do that i can do!
On Wed, May 11, 2011 at 3:09 PM, Robert Xu robxu9@gmail.com wrote:
On Wed, May 11, 2011 at 14:37, PICCORO McKAY Lenz mckaygerhard@gmail.com wrote:
I have that in mind, I am currently focused on SUSE patchs, the most interesting, since the url that i have https://build.opensuse.org/project/packages?project=KDE:KDE3
are the
only who v' ones who remain active to minor maintenance qt3 libraries and others kde3 related projects/soft in fes hours i release a tarball in shutendouji.net
*PLEASE don't use HTML email! It completely screws up my email client*
Why a tarball? We are all merging it to SVN (hopefully).
-- later, Robert Xu
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
i hope some one merge the results in the svn, i dont have a real machine, i connect from a cyber cafe, in live cd, also i dont have 24/7 conections.. i do that i can do!
On Wed, May 11, 2011 at 3:36 PM, PICCORO McKAY Lenz mckaygerhard@gmail.com wrote:
i dont have a real machine, i connect from a cyber cafe, in live cd, also i dont have 24/7 conections.. i do that i can do!
On Wed, May 11, 2011 at 3:09 PM, Robert Xu robxu9@gmail.com wrote:
On Wed, May 11, 2011 at 14:37, PICCORO McKAY Lenz mckaygerhard@gmail.com wrote:
I have that in mind, I am currently focused on SUSE patchs, the most interesting, since the url that i have https://build.opensuse.org/project/packages?project=KDE:KDE3%C2%A0are%C2%A0t... only who v' ones who remain active to minor maintenance qt3 libraries and others kde3 related projects/soft in fes hours i release a tarball in shutendouji.net
*PLEASE don't use HTML email! It completely screws up my email client*
Why a tarball? We are all merging it to SVN (hopefully).
-- later, Robert Xu
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com Cofundador de Venenux; debian based multimedia alike free only zealots users (oh well, i try but..too many free guidelines buahhh) http://shutendouji.net creador de massenkoh linux; debian enhanchements for better up to date support on stable brand, including non-free soft.
-- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com Cofundador de Venenux; debian based multimedia alike free only zealots users (oh well, i try but..too many free guidelines buahhh) http://shutendouji.net creador de massenkoh linux; debian enhanchements for better up to date support on stable brand, including non-free soft.
-
/dev/ammo42 -
David C. Rankin -
PICCORO McKAY Lenz -
Robert Xu