http://permalink.gmane.org/gmane.network.licq.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.network.licq.devel/5037 <pre> Would be interesting to know if this problem was the same as the problem reported on licq-users [1] which I hope is solved on the 1.6-stable branch (which contains the gui-in-main-thread branch). // Erik [1] - http://www.mail-archive.com/licq-users&lt; at &gt;googlegroups.com/msg00331.html </pre> Erik Johansson 2011-12-20T19:45:03 http://permalink.gmane.org/gmane.network.licq.devel/5036 <pre> I compiled gcc 4.2.1 and built qt4-gui with it without any problems. My guess is that you are building qt4-gui against old licq headers. Have you installed licq before building qt4-gui? Are you using the same install prefix? Please describe the steps you took when building licq and plugins and post the output from cmake. // Erik </pre> Erik Johansson 2011-12-18T09:45:09 http://permalink.gmane.org/gmane.network.licq.devel/5035 <pre>Hi I use gcc [09:20]%&gt; gcc -v Using built-in specs. Target: i386-undermydesk-freebsd Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 4.2.1 20070719 [FreeBSD] Erik Johansson писал 16.12.2011 20:44: </pre> Danila 2011-12-17T03:56:48 http://permalink.gmane.org/gmane.network.licq.devel/5034 <pre>Which compiler and version do you use? // Erik On Fri, Dec 16, 2011 at 04:42, Danila &lt;evil&lt; at &gt;mgn.chel.su&gt; wrote: </pre> Erik Johansson 2011-12-16T14:44:31 http://permalink.gmane.org/gmane.network.licq.devel/5033 <pre>Hi I tried to compile it on FreeBSD 8.2-RELEASE-p3, but not compiling plugin qt4-gui Scanning dependencies of target licq_qt4-gui [ 37%] Building CXX object src/CMakeFiles/licq_qt4-gui.dir/config/chat.o [ 37%] Building CXX object src/CMakeFiles/licq_qt4-gui.dir/config/contactlist.o [ 37%] Building CXX object src/CMakeFiles/licq_qt4-gui.dir/config/emoticons.o [ 38%] Building CXX object src/CMakeFiles/licq_qt4-gui.dir/config/general.o [ 38%] Building CXX object src/CMakeFiles/licq_qt4-gui.dir/config/iconmanager.o /tmp/licq-1.6.0/plugins/qt4-gui/src/config/iconmanager.cpp: In member function 'const QPixmap&amp; LicqQtGui::IconManager::iconForEvent(unsigned int)': /tmp/licq-1.6.0/plugins/qt4-gui/src/config/iconmanager.cpp:352: error: 'TypeUrl' is not a member of 'Licq::UserEvent' /tmp/licq-1.6.0/plugins/qt4-gui/src/config/iconmanager.cpp:355: error: 'TypeChat' is not a member of 'Licq::UserEvent' /tmp/licq-1.6.0/plugins/qt4-gui/src/config/iconmanager.cpp:358: error: 'TypeFile' is not a member of 'Licq::</pre> Danila 2011-12-16T03:42:57 http://permalink.gmane.org/gmane.network.licq.devel/5032 <pre> It worked as intended. Thanks a lot! Wedin </pre> M Wedin 2011-11-22T10:32:40 http://permalink.gmane.org/gmane.network.licq.devel/5031 <pre> Yes, it should be executable. Try sudo chmod +x /usr/bin/cdk5-config or su -c 'chmod +x /usr/bin/cdk5-config' // Erik </pre> Erik Johansson 2011-11-21T15:35:00 http://permalink.gmane.org/gmane.network.licq.devel/5030 <pre>2011/11/21 Erik Johansson &lt;erik&lt; at &gt;ejohansson.se&gt;: Certainley! $ ls -la /usr/bin/cdk5-config -rw-r--r-- 1 root root 4343 Nov 20 21:28 /usr/bin/cdk5-config I suppose I need to tweak these rights somehow. Wedin </pre> M Wedin 2011-11-21T15:30:40 http://permalink.gmane.org/gmane.network.licq.devel/5029 <pre> Could you please post the output from "ls -la /usr/bin/cdk5-config". // Erik </pre> Erik Johansson 2011-11-21T15:12:18 http://permalink.gmane.org/gmane.network.licq.devel/5028 <pre>2011/10/30 Anders Olofsson &lt;flynd&lt; at &gt;licq.org&gt;: I tried to compile it on Slackware 13.37, with the aid of a slackbuild script Quote By default the qt4-gui, console, auto-reply and aosd plugins are built. This requires libaosd as well as cdk and can be overridden by setting the PLUGINS environment variable to a space seperated list of auto-reply, forwarder, osd, rms, aosd, console, jabber, msn, qt4-gui. Optional dependencies are cdk for the console, libxosd for the osd and libaosd for the aosd plugin respectivly, all available from SlackBuilds.org. /Quote Initially, I had problems compiling CDK. Writing to the CDK maintainer helped. Editing the version number to the one now valid (5.0_20110517) worked like a charm. CDK installed just fine. Still Licq bailed as follows: ----------------------------- </pre> M Wedin 2011-11-20T22:45:30 http://permalink.gmane.org/gmane.network.licq.devel/5027 <pre> We at least need to provide a command line to the session manager with which it restart the client with the same configuration (which is implemented right now). Besides that, I agree that Licq does not need to store more session state. AFAIK the session id is just passed to the client so that it can restore any state it previously stored under that id. Licq doesn't use this mechanism at all right now, and therefore the parameter could be removed in LicqGui::commitData(). Actually, this would also fix the problem that an additional "-session" parameter is added to the command line on each session restore, i.e. Licq's command line grows longer and longer. Right, that was the problem, it works now. Fiddling with this a bit, I noticed a related issue, which does not appear with the KDE-style shortcut handling: When setting the show/hide shortcut to Alt+I or Meta+I, pressing this shortcut in the Licq main window will switch to the "Ignore" group. Looks like the key event is not consumed completely. ciao </pre> Jörg Mensmann 2011-11-17T20:59:40 http://permalink.gmane.org/gmane.network.licq.devel/5026 <pre> I'm not very familiar with session management but the purpose should be to restore the state of an application as much as possible after a restart. As Licq doesn't have any state handling other than normal configuration I'm not sure it worth pretending anything by having support for the parameter at all. Do you know if the window manager does anything useful for us when the session parameter is present? Otherwise I think it could just as well be removed until someone wants to implement proper session support for Licq. Do you by any chance have Num Lock active? I did some testing and found that the current event grabbing with X only worked if Caps Lock and Num Lock were off. I just committed a fix for this, please check if it works better for you now. Something temporary in the history area sounds complicated (that code is complicated enough as it is). I think I prefer having something in the window rather than messing with the window title or the window icon, so having a pen icon or simila</pre> Anders Olofsson 2011-11-15T19:52:37 http://permalink.gmane.org/gmane.network.licq.devel/5025 <pre>Hi! Anders Olofsson &lt;flynd&lt; at &gt;licq.org&gt; wrote: I couldn't find anything in the KApplication docs. However, all KDE applications only list "--session" as a supported option when called with "--help-qt". Yes, it looks quite incomplete to me, too. The patch is mainly a workaround for the two issues. Without the patch global shortcuts didn't work at all for me, neither with kde4-gui nor with pure qt4-gui. I tried several types of key combos (Meta+I, Ctrl+I, etc.), but they would always go to the window in focus, not Licq. I'm running Fedora 15 with KDE 4.6.5. Well, there is still the contact's name in the tabbar which changes color in this case (if tabs are enabled), but I get the point. Other clients often show a temporary "user is typing" at the end of the chat history. We could also use the pen icon that appears in the contact list as a notification, placing it where the user time display used to be (with a flashy background color). ciao Jörg </pre> Jörg Mensmann 2011-11-14T20:45:32 http://permalink.gmane.org/gmane.network.licq.devel/5024 <pre> Hi, thanks for the patches. I have some comments though. Session handling: According to [1], the -session parameter is mandatory. Is there any KDE documentation indicating that this should be different for KDE applications? Otherwise I would prefer to keep -session but fix the arg parsing instead to handle both "-session" and "-s". Also, now that I look at the current session handling, it will not preserve any parameters for other plugins or licq (for example basedir) so I think this needs a bigger makeover... I'll have to give all of this some more thought... Global shortcuts: The global shortcut works fine with both qt4-gui and kde4-gui here. Is there any specific key(s) that only works when doing it the KDE way? Are you having problems when building without KDE support or only with? Remote time: I'm not against hiding the remote user's time (when unknown or as a user setting) but then we loose the typing notification indicator. I'm open to suggestions on how to show typing notifications instea</pre> Anders Olofsson 2011-11-14T17:26:37 http://permalink.gmane.org/gmane.network.licq.devel/5023 <pre>Hi, here is bunch of patches for the Qt4-GUI that fix session handling and global shortcuts on KDE and make the display of remote user time less intrusive. ciao Jörg ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1_______________________________________________ Licq-devel mailing list Licq-devel&lt; at &gt;licq.org https://lists.sourceforge.net/lists/listinfo/licq-devel </pre> Jörg Mensmann 2011-11-13T18:24:46 http://permalink.gmane.org/gmane.network.licq.devel/5022 <pre>Hi, here is bunch of patches for the Qt4-GUI that fix session handling and global shortcuts on KDE and make the display of remote user time less intrusive. ciao Jörg </pre> Jörg Mensmann 2011-11-13T18:31:53 http://permalink.gmane.org/gmane.network.licq.devel/5021 <pre>The final release of Licq 1.6.0 is here. Licq 1.6.0 contains both bugfixes and new features. Download and release notes: http://sourceforge.net/projects/licq/files/licq/1.6.0/ The Licq Team </pre> Anders Olofsson 2011-10-30T11:57:02 http://permalink.gmane.org/gmane.network.licq.devel/5020 <pre>The first release candidate for Licq 1.6.0 is ready for download. Licq 1.6.0 contains both bugfixes and new features. Download and release notes: http://sourceforge.net/projects/licq/files/licq/1.6.0/ If you find any bugs, please notify us by creating an Issue in github: https://github.com/licq-im/licq/issues?sort=created&amp;direction=desc&amp;state=open The Licq Team </pre> Anders Olofsson 2011-10-16T18:55:57 http://permalink.gmane.org/gmane.network.licq.devel/5019 <pre> Alright, two more in the trash that we can forget. I don't have the ticket attachments but reading the commit headings for 2007 I could not find anything that seems to be related to this so I guess it didn't get committed. I'm not sure if I want to see the patches or if we just should consider this as unconfirmed unless someone can verify with icq 5.1 that it's still a problem. Nope, nothing related in the following month. Unless Eugene (or anyone else) has anything to add this stays in the unconfirmed list. The list of unconfirmed bugs is now down to only 15 of the 82 tickets open when trac closed. I'll wait a bit more and see if I get any more helpful replies here then I'll post on licq-users for help with descriptions of what needs to be tested to confirm/reject them and see if we can reduce the number a bit more before throwing them away just because we're unsure... /Anders </pre> Anders Olofsson 2011-08-08T18:34:44 http://permalink.gmane.org/gmane.network.licq.devel/5018 <pre> I left it open as a TODO to investigate if it could be done using a different method. I believe it can be closed and if desired, opened as a new ticket. Licq was sending packets in a different order than the official client. It could have been used to detect non-official clients and block them. But it looks like that never happened, so it is irrelevant. I do not recall, you would have to use git grep to see if the changes are in or not. Don't remember this either, looking at gig log for my commits after that day should reveal if it was done or not. Jon </pre> Jon Keating 2011-08-07T22:03:06 http://permalink.gmane.org/gmane.network.licq.devel/5017 <pre> Yes, I agree, and this should reduce the list a bit. Some of our timestamps are provided by the server and some are tracked locally and depend on when we logged in etc so I think we can assume this is the reason for the confusion and move this to the forget-it-list. The only solution I can think of would require Licq to keep a log of all changes and use that to figure out if a change was local or from the server (i.e. another client) and merge based on that. To me this sounds complicated and is either a low-prio enhancement or skip it. My vote is to forget it and just accept it as a limitation when using multiple client/instances for the same account. Ok, the ticket isn't very detailed anyway If a user changes encoding it doesn't mean it should apply to previous messages, so I'll just drop this one. The complaint here is that spammers are added to list but I haven't seen same as messages in a long time now (just as authorization requests) so I'm guessing it's not as important any longer. The </pre> Anders Olofsson 2011-08-07T15:04:33 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.network.licq.devel