dhamp
dhamp
_From [[email protected]](https://code.google.com/u/113270270180924107928/) on November 14, 2011 08:03:41_ Exact similar problems faced in linux eiskaltdcpp-qt 2.3.
_From [[email protected]](https://code.google.com/u/102614106087232079264/) on November 14, 2011 08:05:30_ Hmm, I will try to launch program in Wine later. It should work there.
_From [[email protected]](https://code.google.com/u/105808192259708326911/) on November 14, 2011 08:11:39_ @technik, actually i am trying in Wine using win version (EiskaltDC++-2.2.4-x86-portable.zip) where i am facing this problem (even i tried on another win...
_From [[email protected]](https://code.google.com/u/102614106087232079264/) on November 14, 2011 12:44:45_ I have just tested lua scripts and here is sad results: 1) Lua scripts don't work on my system in Qt UI completely...
_From [[email protected]](https://code.google.com/u/102614106087232079264/) on November 14, 2011 12:45:39_ s/kernel/core/
_From [[email protected]](https://code.google.com/u/102614106087232079264/) on November 14, 2011 13:03:16_ Hmm, this is very strange bug. I have launched Qt UI after Gtk UI and suddenly scripts are working in it.
_From [[email protected]](https://code.google.com/u/102614106087232079264/) on November 14, 2011 13:05:32_ Just execute /help to see that scripts were loaded and execute /uptime to see that they can work.
_From [[email protected]](https://code.google.com/u/102614106087232079264/) on November 14, 2011 14:49:12_ Another developer wrote that he had tested portable version of program successfully in Wine: 1) Move directory EiskaltDC++_Win32_portable\resources\luascripts to EiskaltDC++_Win32_portable\luascripts 2) ... 3)...
_From [[email protected]](https://code.google.com/u/105808192259708326911/) on November 15, 2011 07:51:56_ Yayy ... shifting the directory worked (i guess). Thanks @technik :) But the main problem is where can i see the System logs...
_From [[email protected]](https://code.google.com/u/102614106087232079264/) on November 15, 2011 08:02:36_ DC():PrintDebug messages are visible only in Debug build of program. You should use something else to browse the script activity. We could make...