KMessageBox::queuedMessageBox(this->tqparentWidget(),KMessageBox::Information,i18n("The Chat Window style was successfully installed."),i18n("Install successful"));
KMessageBox::queuedMessageBox(this->parentWidget(),KMessageBox::Information,i18n("The Chat Window style was successfully installed."),i18n("Install successful"));
returntrue;
}
caseChatWindowStyleManager::StyleCannotOpen:
{
KMessageBox::queuedMessageBox(this->tqparentWidget(),KMessageBox::Error,i18n("The specified archive cannot be opened.\nMake sure that the archive is valid ZIP or TAR archive."),i18n("Cannot open archive"));
KMessageBox::queuedMessageBox(this->parentWidget(),KMessageBox::Error,i18n("The specified archive cannot be opened.\nMake sure that the archive is valid ZIP or TAR archive."),i18n("Cannot open archive"));
KMessageBox::queuedMessageBox(this->tqparentWidget(),KMessageBox::Error,i18n("Could not find a suitable place to install the Chat Window style in user directory."),i18n("Cannot find styles directory"));
KMessageBox::queuedMessageBox(this->parentWidget(),KMessageBox::Error,i18n("Could not find a suitable place to install the Chat Window style in user directory."),i18n("Cannot find styles directory"));
break;
}
caseChatWindowStyleManager::StyleNotValid:
{
KMessageBox::queuedMessageBox(this->tqparentWidget(),KMessageBox::Error,i18n("The specified archive does not contain a valid Chat Window style."),i18n("Invalid Style"));
KMessageBox::queuedMessageBox(this->parentWidget(),KMessageBox::Error,i18n("The specified archive does not contain a valid Chat Window style."),i18n("Invalid Style"));
break;
}
caseChatWindowStyleManager::StyleUnknow:
default:
{
KMessageBox::queuedMessageBox(this->tqparentWidget(),KMessageBox::Error,i18n("An unknow error occurred while trying to install the Chat Window style."),i18n("Unknow error"));
KMessageBox::queuedMessageBox(this->parentWidget(),KMessageBox::Error,i18n("An unknow error occurred while trying to install the Chat Window style."),i18n("Unknow error"));
(CBshred,i18n("<b>Shred source file</b>: permanently remove source file. No recovery will be possible"));
TQStringshredWhatsThis=i18n("<qt><b>Shred source file:</b><br /><p>Checking this option will shred (overwrite several times before erasing) the files you have encrypted. This way, it is almost impossible that the source file is recovered.</p><p><b>But you must be aware that this is not secure</b> on all file systems, and that parts of the file may have been saved in a temporary file or in the spooler of your printer if you previously opened it in an editor or tried to print it. Only works on files (not on folders).</p></qt>");
KActiveLabel*warn=newKActiveLabel(i18n("<a href=\"whatsthis:%1\">Read this before using shredding</a>").tqarg(shredWhatsThis),tqparentBox );
KActiveLabel*warn=newKActiveLabel(i18n("<a href=\"whatsthis:%1\">Read this before using shredding</a>").tqarg(shredWhatsThis),parentBox );
kdWarning(GROUPWISE_DEBUG_GLOBAL)<<" - received a nested folder. These were not supported in GroupWise or Kopete as of Sept 2004, aborting! (tqparentId = "<<folder.tqparentId <<")"<<endl;
kdWarning(GROUPWISE_DEBUG_GLOBAL)<<" - received a nested folder. These were not supported in GroupWise or Kopete as of Sept 2004, aborting! (parentId = "<<folder.parentId <<")"<<endl;
kdDebug(GROUPWISE_DEBUG_GLOBAL)<<" = CONTACT '"<<contact->nickName()<<"' IS IN "<<contact->metaContact()->groups().count()<<" MC GROUPS, AND HAS "<<m_serverListModel->instancesWithDn(contact->dn()).count()<<" CONTACT LIST INSTANCES."<<endl;
kdDebug(GROUPWISE_DEBUG_GLOBAL)<<" = LOOKING FOR NOOP GROUP MEMBERSHIPS"<<endl;
// 1) Seek matches between CLIs and MCGs and remove from the lists without taking any action. match on objectid, tqparentid
// 1) Seek matches between CLIs and MCGs and remove from the lists without taking any action. match on objectid, parentid
// 2) Each remaining unmatched pair is a move, initiate and remove - need to take care to always use greatest unused sequence number - if we have to set the sequence number to the following sequence number within the folder, we may have a problem where after the first move, we have to wait for the state of the CLIs to be updated pending the completion of the first move - this would be difficult to cope with, because our current lists would be out of date, or we'd have to restart the sync - assuming the first move created a new matched CLI-MCG pair, we could do that with little cost.
// 3) Any remaining entries in MCG list are adds, carry out
// 4) Any remaining entries in CLI list are removes, carry out