大神们 弱弱问一句 cf那个活动和qt语音有关啊？_穿越火线吧_百度贴吧
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&签到排名：今日本吧第个签到，本吧因你更精彩，明天继续来努力！
本吧签到人数：0成为超级会员，使用一键签到本月漏签0次！成为超级会员，赠送8张补签卡连续签到：天&&累计签到：天超级会员单次开通12个月以上，赠送连续签到卡3张
关注：2,802,561贴子：
大神们 弱弱问一句 cf那个活动和qt语音有关啊？收藏
大神们 弱弱问一句 cf那个活动和有关啊？或者给我讲解一下 怎么才能领qt装备？
1楼 20:43&|
相关的贴子107415538相关的图贴
本吧贡献榜 登录百度帐号推荐应用
内&&容:使用签名档&&
为兴趣而生，贴吧更懂你。&或QT语音的会员有谁知道是怎么弄的啊？？是要开通的还是怎么弄的啊？？？详细。。。。。谢谢_百度知道
QT语音的会员有谁知道是怎么弄的啊？？是要开通的还是怎么弄的啊？？？详细。。。。。谢谢
我有更好的答案
按默认排序
不是开通的，叫房间的管理员可以给你提拔为会员以及嘉宾的。祝您好运！
其他类似问题
11人觉得有用
qt语音的相关知识
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁qt 关于 Object:connect: No such slot QDialog:findClicked()解决思路_unchecked exception和checked exception,该怎么处理_VC++出现内存异常，请教大神们解答下__脚本百事通
稍等，加载中……
^_^请注意，有可能下面的2篇文章才是您想要的内容：
qt 关于 Object:connect: No such slot QDialog:findClicked()解决思路
unchecked exception和checked exception,该怎么处理
VC++出现内存异常，请教大神们解答下
qt 关于 Object:connect: No such slot QDialog:findClicked()解决思路
qt 关于 Object::connect: No such slot QDialog::findClicked()---------------------main.cpp---------------------
#include &QApplication.h&
#include "finddialog.h"
int main(int argc, char *argv[])
QApplication app(argc, argv);
FindDialog *dialog = new FindD
dialog-&show();
return app.exec();
-----------------------Finddialog.h-------------------
#ifndef FINDDIALOG_H
#define FINDDIALOG_H
#include &QDialog.h&
class QCheckB
class QLineE
class QPushB
class FindDialog : public QDialog
// Q_OBJECT
FindDialog(QWidget *parent = 0);
void findNext(const QString &str, Qt::CaseSensitivity cs);
void findPrevious(const QString &str, Qt::CaseSensitivity cs);
private slots:
void findClicked();
void enableFindButton(const QString &text);
QLineEdit *lineE
QCheckBox *caseCheckB
QCheckBox *backwardCheckB
QPushButton *findB
QPushButton *closeB
---------------------------finddialog.cpp------------------------
#include &QtGui&
#include "finddialog.h"
FindDialog::FindDialog(QWidget *parent)
: QDialog(parent)
label = new QLabel(tr("Find &what:"));
lineEdit = new QLineE
label-&setBuddy(lineEdit);
caseCheckBox = new QCheckBox(tr("Match &case"));
backwardCheckBox = new QCheckBox(tr("Search &backward"));
findButton = new QPushButton(tr("&Find"));
findButton-&setDefault(true);
findButton-&setEnabled(false);
closeButton = new QPushButton(tr("Close"));
connect(lineEdit, SIGNAL(textChanged(const QString &)),
this, SLOT(enableFindButton(const QString &)));
connect(findButton, SIGNAL(clicked()),
this, SLOT(findClicked()));
connect(closeButton, SIGNAL(clicked()),
this, SLOT(findClicked()));
QHBoxLayout *topLeftLayout = new QHBoxL
topLeftLayout-&addWidget(label);
topLeftLayout-&addWidget(lineEdit);
QVBoxLayout *leftLayout = new QVBoxL
leftLayout-&addLayout(topLeftLayout);
leftLayout-&addWidget(caseCheckBox);
leftLayout-&addWidget(backwardCheckBox);
QVBoxLayout *rightLayout = new QVBoxL
rightLayout-&addWidget(findButton);
rightLayout-&addWidget(closeButton);
rightLayout-&addStretch();
QHBoxLayout *mainLayout = new QHBoxL
mainLayout-&addLayout(leftLayout);
mainLayout-&addLayout(rightLayout);
setLayout(mainLayout);
setWindowTitle(tr("Find"));
setFixedHeight(sizeHint().height());
void FindDialog::findClicked()
QMessageBox::question(this,"quit","quit",QMessageBox::Ok | QMessageBox::Cancel ,QMessageBox::Ok);
QString text = lineEdit-&text();
Qt::CaseSensitivity cs =
caseCheckBox-&isChecked() ? Qt::CaseSensitive
: Qt::CaseI
if (backwardCheckBox-&isChecked()) {
emit findPrevious(text, cs);
emit findNext(text, cs);
void FindDialog::enableFindButton(const QString &text)
findButton-&setEnabled(!text.isEmpty());
void FindDialog::findNext(const QString &str, Qt::CaseSensitivity cs)
QMessageBox::question(this,"quit","quit",QMessageBox::Ok | QMessageBox::Cancel ,QMessageBox::Ok);
void FindDialog::findPrevious(const QString &str, Qt::CaseSensitivity cs)
QMessageBox::question(this,"quit","quit",QMessageBox::Ok | QMessageBox::Cancel ,QMessageBox::Ok);
如上代码是C++GUI Qt4编程第二版的。 随书源代码的第二章的一个find列子。
我用arm-hismall-linux-g++编译好了。在hi3515板子上跑的时候怎么总是提示Object::connect: No such slot QDialog::findClicked() 这个呢。 是哪个信号-槽的问题，能编译能运行，但是按钮没有相应，应该是信号-槽的设置没好。 各位高手达人们，求解答。
------解决方案--------------------// Q_OBJECT
去掉注释看看------解决方案--------------------// Q_OBJECT
你犯错误了，这个宏必须有！！！
在有你自定义signal和slots的Qt派生类里必须有这个宏。这可是Qt最基本原则------解决方案--------------------// Q_OBJECT
去掉注释，使用信号槽机制必须要有Q_OBJECT
并使用moc生成文件------解决方案--------------------
引用:// Q_OBJECT
去掉注释看看
去掉后，用moc编译后，生成了moc_源文件， 在用arm-hismall-linux-g++编译的时候，moc_源文件报错。 还提示moc编译器 版本低了。 这个宏应该不会影响吧。
我自己实现了信号的代码。
我也不清楚，哪个Q_OBJECT 有没有影响的。
这样的话只好升级QtSDK版本喽。------解决方案--------------------Q_OBJECT不能省的。。要不就没有meta信息了。
unchecked exception和checked exception,该怎么处理
unchecked exception和checked exception一直没搞明白为何把异常分成unchecked exception和checked exception两类。刚刚反复看api，我有这样一种感觉，不知想的对不对，还望大家指教啊：RuntimeException和他的子类貌似都是因为程序设计上有错误导致的，比如：IllegalMonitorStateException
这是同步机制使用的不正确IndexOutOfBoundsException
数组用的不对NullPointerException 没初始化等等还有很多。=====================================================我又看了看checked exception，他们都是java程序本身控制不了的，但是又不能不应对的异常，比如：SQLException api解释：An exception that provides information on a database access error or other errors 数据库造成的FileNotFoundException
文件系统造成的SocketException
Signals that an error occurred while attempting to connect a socket to a remote address and port. Typically, the connection was refused remotely 这是socket服务器的原因。大家拍砖，指条明路吧，大侠们 谢谢------解决方案--------------------
Java中的异常分为受检查的异常和不受检查的异常。（1）受检查的异常：这种在编译时被强制检查的异常称为"受检查的异常"。即在方法的声明中声明的异常。（2）不受检查的异常：在方法的声明中没有声明，但在方法的运行过程中发生的各种异常被称为"不被检查的异常"。这种异常是错误，会被自动捕获。一些规模较小的程序中，受检查的异常能够提高开发效率，但随着项目规模的扩大，过多的受检查的异常将变的难以管理，其带来的好处也将消失殆尽。
VC++出现内存异常，请教大神们解答下
VC++出现内存错误，请问大神们解答下如何确定是出现内存泄漏？怎样找到出错的语句？解决方案有什么？小弟初学，望大神指导下。最好有几份文档给我参考下。（积分不够了，能分配下去的分数不多，请大家见谅下）
------解决方案--------------------在vs输出窗口会有leak memeory的信息，但是不能直接定位的泄露行。
发现内存泄露时，我一般习惯把new或者malloc的地方打印出来，然后把delete或者free的地方打印出来，然后成对的对比，就会发现泄露的地方了。------解决方案--------------------可使用VLD：/Articles/9815/Visual-Leak-Detector-Enhanced-Memory-Leak-Detectio------解决方案--------------------任务管理器看进程的内存是否一直增长，一直增长可能就泄漏了。如果出现泄漏，逐段屏蔽可能泄漏的代码，屏蔽不泄漏了，那被屏蔽的代码可能就存在问题。------解决方案--------------------_CrtDumpMemoryLeaks
Dumps all of the memory blocks in the debug heap when a memory leak has occurred (debug version only).
int _CrtDumpMemoryLeaks( void );
Routine Required Header Compatibility
_CrtDumpMemoryLeaks &crtdbg.h& Win NT, Win 95
For additional compatibility information, see Compatibility in the Introduction.
LIBCD.LIB Single thread static library, debug version
LIBCMTD.LIB Multithread static library, debug version
MSVCRTD.LIB Import library for MSVCRTD.DLL, debug version
Return Value
_CrtDumpMemoryLeaks returns TRUE if a
otherwise, the function returns FALSE.
The _CrtDumpMemoryLeaks function determines whether a memory leak has occurred since the start of program execution. When a leak is found, the debug header information for all of the objects in the heap is dumped in a user-readable form. When _DEBUG is not defined, calls to _CrtDumpMemoryLeaks are removed during preprocessing.
_CrtDumpMemoryLeaks is frequently called at the end of program execution to verify that all memory allocated by the application has been freed. The function can be called automatically at program termination by turning on the _CRTDBG_LEAK_CHECK_DF bit field of the _crtDbgFlag flag using the _CrtSetDbgFlag function.
_CrtDumpMemoryLeaks calls _CrtMemCheckpoint to obtain the current state of the heap and then scans the state for blocks that have not been freed. When an unfreed block is encountered, _CrtDumpMemoryLeaks calls _CrtMemDumpAllObjectsSince to dump information for all of the objects allocated in the heap from the start of program execution.
By default, internal C run-time blocks (_CRT_BLOCK) are not included in memory dump operations. The _CrtSetDbgFlag function can be used to turn on the _CRTDBG_CHECK_CRT_DF bit of _crtDbgFlag to include these blocks in the leak detection process.
For more information about heap state functions and the _CrtMemState structure, see the Heap State Reporting Functions. For information about how memory blocks are allocated, initialized, and managed in the debug version of the base heap, see Memory Management and the Debug Heap.
/*****************************************************************
This simple program illustrates the basic debugging features *
of the C runtime libraries, and the kind of debug output
that these features generate.
*****************************************************************/
#include &stdio.h&
#include &string.h&
#include &malloc.h&
#include &crtdbg.h&
// This routine place comments at the head of a section of debug output
void OutputHeading( const char * explanation )
_RPT1( _CRT_WARN, "\n\n%s:\n**************************************\
************************************\n", explanation );
// The following macros set and clear, respectively, given bits
// of the C runtime library debug flag, as specified by a bitmask.
SET_CRT_DEBUG_FIELD(a) \
_CrtSetDbgFlag((a) ------解决方案-------------------- _CrtSetDbgFlag(_CRTDBG_REPORT_FLAG))
CLEAR_CRT_DEBUG_FIELD(a) \
_CrtSetDbgFlag(~(a) & _CrtSetDbgFlag(_CRTDBG_REPORT_FLAG))
SET_CRT_DEBUG_FIELD(a)
((void) 0)
CLEAR_CRT_DEBUG_FIELD(a) ((void) 0)
void main( )
char *p1, *p2;
_CrtMemState s1, s2, s3;
// Send all reports to STDOUT
_CrtSetReportMode( _CRT_WARN, _CRTDBG_MODE_FILE );
_CrtSetReportFile( _CRT_WARN, _CRTDBG_FILE_STDOUT );
_CrtSetReportMode( _CRT_ERROR, _CRTDBG_MODE_FILE );
_CrtSetReportFile( _CRT_ERROR, _CRTDBG_FILE_STDOUT );
_CrtSetReportMode( _CRT_ASSERT, _CRTDBG_MODE_FILE );
_CrtSetReportFile( _CRT_ASSERT, _CRTDBG_FILE_STDOUT );
// Allocate 2 memory blocks and store a string in each
p1 = malloc( 34 );
strcpy( p1, "This is the p1 string (34 bytes)." );
p2 = malloc( 34 );
strcpy( p2, "This is the p2 string (34 bytes)." );
OutputHeading(
"Use _ASSERTE to check that the two strings are identical" );
_ASSERTE( strcmp( p1, p2 ) == 0 );
OutputHeading(
"Use a _RPT macro to report the string contents as a warning" );
_RPT2( _CRT_WARN, "p1 points to '%s' and \np2 points to '%s'\n", p1, p2 );
OutputHeading(
"Use _CRTMemDumpAllObjectsSince to check the p1 and p2 allocations" );
_CrtMemDumpAllObjectsSince( NULL );
free( p2 );
OutputHeading(
"Having freed p2, dump allocation information about p1 only" );
_CrtMemDumpAllObjectsSince( NULL );
// Store a memory checkpoint in the s1 memory-state structure
_CrtMemCheckpoint( &s1 );
// Allocate another block, pointed to by p2
p2 = malloc( 38 );
strcpy( p2, "This new p2 string occupies 38 bytes.");
// Store a 2nd memory checkpoint in s2
_CrtMemCheckpoint( &s2 );
OutputHeading(
"Dump the changes that occurred between two memory checkpoints" );
if ( _CrtMemDifference( &s3, &s1, &s2 ) )
_CrtMemDumpStatistics( &s3 );
// Free p2 again and store a new memory checkpoint in s2
free( p2 );
_CrtMemCheckpoint( &s2 );
OutputHeading(
"Now the memory state at the two checkpoints is the same" );
if ( _CrtMemDifference( &s3, &s1, &s2 ) )
_CrtMemDumpStatistics( &s3 );
strcpy( p1, "This new p1 string is over 34 bytes" );
OutputHeading( "Free p1 after overwriting the end of the allocation" );
free( p1 );
// Set the debug-heap flag so that freed blocks are kept on the
// linked list, to catch any inadvertent use of freed memory
SET_CRT_DEBUG_FIELD( _CRTDBG_DELAY_FREE_MEM_DF );
p1 = malloc( 10 );
free( p1 );
strcpy( p1, "Oops" );
OutputHeading( "Perform a memory check after corrupting freed memory" );
_CrtCheckMemory( );
// Use explicit calls to _malloc_dbg to save file name and line number
// information, and also to allocate Client type blocks for tracking
p1 = _malloc_dbg( 40, _NORMAL_BLOCK, __FILE__, __LINE__ );
p2 = _malloc_dbg( 40, _CLIENT_BLOCK, __FILE__, __LINE__ );
strcpy( p1, "p1 points to a Normal allocation block" );
strcpy( p2, "p2 points to a Client allocation block" );
// You must use _free_dbg to free a Client block
OutputHeading(
"Using free( ) to free a Client block causes an assertion failure" );
free( p1 );
free( p2 );
p1 = malloc( 10 );
OutputHeading( "Examine outstanding allocations (dump memory leaks)" );
_CrtDumpMemoryLeaks( );
// Set the debug-heap flag so that memory leaks are reported when
// the process terminates. Then, exit.
OutputHeading( "Program exits without freeing a memory block" );
SET_CRT_DEBUG_FIELD( _CRTDBG_LEAK_CHECK_DF );
Use _ASSERTE to check that the two strings are identical:
**************************************************************************
C:\DEV\EXAMPLE1.C(56) : Assertion failed: strcmp( p1, p2 ) == 0
Use a _RPT macro to report the string contents as a warning:
**************************************************************************
p1 points to 'This is the p1 string (34 bytes).' and
p2 points to 'This is the p2 string (34 bytes).'
Use _CRTMemDumpAllObjectsSince to check the p1 and p2 allocations:
**************************************************************************
Dumping objects -&
{13} normal block at 0x00660B5C, 34 bytes long
Data: &This is the p2 s& 54 68 69 73 20 69 73 20 74 68 65 20 70 32 20 73
{12} normal block at 0x bytes long
Data: &This is the p1 s& 54 68 69 73 20 69 73 20 74 68 65 20 70 31 20 73
Object dump complete.
Having freed p2, dump allocation information about p1 only:
**************************************************************************
Dumping objects -&
{12} normal block at 0x bytes long
Data: &This is the p1 s& 54 68 69 73 20 69 73 20 74 68 65 20 70 31 20 73
Object dump complete.
Dump the changes that occurred between two memory checkpoints:
**************************************************************************
0 bytes in 0 Free Blocks.
38 bytes in 1 Normal Blocks.
0 bytes in 0 CRT Blocks.
0 bytes in 0 IgnoreClient Blocks.
0 bytes in 0 (null) Blocks.
Largest number used: 4 bytes.
Total allocations: 38 bytes.
Now the memory state at the two checkpoints is the same:
**************************************************************************
Free p1 after overwriting the end of the allocation:
**************************************************************************
memory check error at 0x00660B32 = 0x73, should be 0xFD.
memory check error at 0x00660B33 = 0x00, should be 0xFD.
DAMAGE: after Normal block (#12) at 0x00660B10.
Perform a memory check after corrupting freed memory:
**************************************************************************
memory check error at 0x00660B10 = 0x4F, should be 0xDD.
memory check error at 0x00660B11 = 0x6F, should be 0xDD.
memory check error at 0x00660B12 = 0x70, should be 0xDD.
memory check error at 0x00660B13 = 0x73, should be 0xDD.
memory check error at 0x00660B14 = 0x00, should be 0xDD.
DAMAGE: on top of Free block at 0x00660B10.
DAMAGED located at 0x00660B10 is 10 bytes long.
Using free( ) to free a Client block causes an assertion failure:
**************************************************************************
dbgheap.c(1039) : Assertion failed: pHead-&nBlockUse == nBlockUse
Examine outstanding allocations (dump memory leaks):
**************************************************************************
Detected memory leaks!
Dumping objects -&
{18} normal block at 0x0 bytes long
& CD CD CD CD CD CD CD CD CD CD
Object dump complete.
Program exits without freeing a memory block:
**************************************************************************
Detected memory leaks!
Dumping objects -&
{18} normal block at 0x0 bytes long
& CD CD CD CD CD CD CD CD CD CD
Object dump complete.
Debug Functions
如果您喜欢IT行业或者对IT行业感兴趣，想开拓技术视野，欢迎加入本站官方QQ群：，在群里认识新朋友和交流技术^_^
本站联系邮箱：qt语音个人贡献怎么算求大神帮助_百度知道
qt语音个人贡献怎么算求大神帮助
提问者采纳
1个小时一点贡献。
其他类似问题
qt语音的相关知识
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁我现在在QT一个频道当上了红马，要放歌的但是有问题求大神解决_百度知道
我现在在QT一个频道当上了红马，要放歌的但是有问题求大神解决
我一上麦把背景音乐（酷狗音乐）放了歌 麦下的人说我声音卡卡的 背景音乐也卡 ，但是我网络延迟才89 丢包0% 我自己听着也不卡 为什么麦下的人听着说好卡 ，（在接待大厅放歌 400人起码有） 求懂的大神 解决问题
提问者采纳
语音设置里面 修改下那个设备信息 试试
常规语音聊天提示音背景音乐 哪个？
扬声器 里面有没有一个选择 是 主声音驱动程序
conex 什么的 那个 如果没有的话 这个就真心不知道了.
常规麦克风设置：主声音捕获驱动程序麦克风（一堆英文设备）（我选的这个）扬声器设置：主声音驱动程序（我选的这个）耳机（一堆英文设备）扬声器（一堆英文设备）
你在扬声器选那个 耳机 跟扬声器 分别试试.
如果不行的话 哥们也帮不了你了~亲
提问者评价
按照你说的，真的成功了，好开心，谢谢你！
其他类似问题
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁