Some documentation updates.

This commit is contained in:
LoRd_MuldeR 2015-08-22 15:12:50 +02:00
parent 0bc5667776
commit fe0841fae8
19 changed files with 2940 additions and 2862 deletions

View File

@ -111,13 +111,13 @@ document.write('<a h'+'ref'+'="ma'+'ilto'+':'+e+'">'+e+'<\/'+'a'+'>');
<h2 id="platform-support"><span class="header-section-number">1.1</span> Platform Support</h2> <h2 id="platform-support"><span class="header-section-number">1.1</span> Platform Support</h2>
<p><strong>Tier #1:</strong> LameXP is currently being developed on the following platforms:</p> <p><strong>Tier #1:</strong> LameXP is currently being developed on the following platforms:</p>
<ul> <ul>
<li>Microsoft Windows 8.1, 32-Bit and 64-Bit editions<br /></li> <li>Microsoft Windows 10, 32-Bit and 64-Bit editions<br /></li>
<li>Microsoft Windows 7 with Service Pack 1, 32-Bit and 64-Bit editions<br /></li> <li>Microsoft Windows 7 with Service Pack 1, 32-Bit and 64-Bit editions<br /></li>
<li>Microsoft Windows XP with Service Pack 3 <strong>(see remarks)</strong></li> <li>Microsoft Windows XP with Service Pack 3 <strong>(see remarks)</strong></li>
</ul> </ul>
<p><strong>Tier #2:</strong> The following platforms should work too, but aren't tested extensively:</p> <p><strong>Tier #2:</strong> The following platforms should work too, but aren't tested extensively:</p>
<ul> <ul>
<li>Microsoft Windows 10, 32-Bit and 64-Bit editions<br /></li> <li>Microsoft Windows 8.1, 32-Bit and 64-Bit editions<br /></li>
<li>Microsoft Windows 8.0, 32-Bit and 64-Bit editions<br /></li> <li>Microsoft Windows 8.0, 32-Bit and 64-Bit editions<br /></li>
<li>Microsoft Windows Vista with Service Pack 2, 32-Bit and 64-Bit editions<br /></li> <li>Microsoft Windows Vista with Service Pack 2, 32-Bit and 64-Bit editions<br /></li>
<li>Microsoft Windows XP x64 Edition with Service Pack 2<br /></li> <li>Microsoft Windows XP x64 Edition with Service Pack 2<br /></li>
@ -210,7 +210,9 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.<
<p>At this point, it should be clear that implementing <em>workarounds</em> for defective anti-virus software is <strong>not</strong> a viable option for application developers. Instead, since the <a href="http://en.wikipedia.org/wiki/Antivirus_software#Problems_caused_by_false_positives"><strong>false positive</strong></a> is an error (bug) in the particular <em>anti-virus software</em>, it can be fixed <em>only</em> by the developer of the anti-virus software. Therefore, it is important that <em>you</em>, the (paying) customer of the anti-virus company, contact the support team of the anti-virus company and report the problem to them! Most anti-virus companies provide ways to report <em>false positives</em> in a standardized way, e.g. by means of a <a href="http://en.wikipedia.org/wiki/Form_%28HTML%29">webform</a>. However, it is <em>not</em> possible to list them all here. So please refer to the anti-virus developer's web-site. Also, when reporting <em>false positives</em>, please be self-confident: As a paying customer, you can demand that <em>false positives</em> get fixed in a timely manner. Otherwise, get your money back!</p> <p>At this point, it should be clear that implementing <em>workarounds</em> for defective anti-virus software is <strong>not</strong> a viable option for application developers. Instead, since the <a href="http://en.wikipedia.org/wiki/Antivirus_software#Problems_caused_by_false_positives"><strong>false positive</strong></a> is an error (bug) in the particular <em>anti-virus software</em>, it can be fixed <em>only</em> by the developer of the anti-virus software. Therefore, it is important that <em>you</em>, the (paying) customer of the anti-virus company, contact the support team of the anti-virus company and report the problem to them! Most anti-virus companies provide ways to report <em>false positives</em> in a standardized way, e.g. by means of a <a href="http://en.wikipedia.org/wiki/Form_%28HTML%29">webform</a>. However, it is <em>not</em> possible to list them all here. So please refer to the anti-virus developer's web-site. Also, when reporting <em>false positives</em>, please be self-confident: As a paying customer, you can demand that <em>false positives</em> get fixed in a timely manner. Otherwise, get your money back!</p>
<h2 id="performance-issues"><span class="header-section-number">3.2</span> Performance Issues</h2> <h2 id="performance-issues"><span class="header-section-number">3.2</span> Performance Issues</h2>
<p>During the <em>startup procedure</em>, the LameXP software has to perform a number of <em>file-system</em> operations. This can take a few moments. However, the startup procedure should <strong>never</strong> take longer than <em>approximately</em> 5 seconds. Even on our test system Windows 7 running on an <em>ancient</em> Intel Core2 processor with 4 GB of RAM the startup procedure takes only about 1.5 seconds. And that is with the &quot;real-time protection&quot; of Microsoft Security Essentials (MSE) enabled! If we disable the MSE &quot;real-time protection&quot; feature, the startup procedure takes less than 0.5 seconds. <em>Unfortunately</em>, it has been brought to our attention, that some other anti-virus products may <em>slow down</em> the startup procedure significantly! Startup delays of up to 20 seconds have been reported by users, which corresponds to a slow down factor of <strong>40×</strong> caused by the anti-virus software!</p> <p>During the <em>startup procedure</em>, the LameXP software has to perform a number of <em>file-system</em> operations. This can take a few moments. However, the startup procedure should <strong>never</strong> take longer than <em>approximately</em> 5 seconds. Even on our test system Windows 7 running on an <em>ancient</em> Intel Core2 processor with 4 GB of RAM the startup procedure takes only about 1.5 seconds. And that is with the &quot;real-time protection&quot; of Microsoft Security Essentials (MSE) enabled! If we disable the MSE &quot;real-time protection&quot; feature, the startup procedure takes less than 0.5 seconds. <em>Unfortunately</em>, it has been brought to our attention, that some other anti-virus products may <em>slow down</em> the startup procedure significantly! Startup delays of up to 20 seconds have been reported by users, which corresponds to a slow down factor of <strong>40×</strong> caused by the anti-virus software!</p>
<p>Consequently, if you think that LameXP is starting up &quot;slow&quot; on your machine, we recommend to <em>temporarily</em> <strong>disable</strong> or <strong>uninstall</strong> your current anti-virus software. If your anti-virus software has a so-called &quot;real-time protection&quot; or &quot;guard&quot; feature, please be sure to <em>deactivate</em> that feature too! As soon as the anti-virus software has been <em>neutralized</em> and <strong>no</strong> longer affects legitimate applications, please try launching the LameXP software again. If it turns out that the startup procedure of LameXP has become significantly <em>faster</em> when the anti-virus software is <strong>not</strong> interfering, then you know one thing for sure: It is the <em>anti-virus software</em> that was causing the slow down! Please recognize that <em>we</em> can <strong>not</strong> fix this kind of problems. Instead, since the problem is actually a <em>defect</em> of the anti-virus software, please report the problem to the developer of the <em>anti-virus software</em>!</p> <p>Consequently, if you think that LameXP is starting up &quot;slow&quot; on your machine, we recommend to <strong>temporarily</strong> <em>disable</em> or <em>uninstall</em> your current anti-virus software. If your anti-virus software has a so-called &quot;real-time protection&quot; or &quot;guard&quot; feature, please be sure to <em>deactivate</em> that feature too! As soon as the anti-virus software has been <em>neutralized</em> and <strong>no</strong> longer affects legitimate applications, please try launching the LameXP software again. If it turns out that the startup procedure of LameXP has become significantly <em>faster</em> when the anti-virus software is <strong>not</strong> interfering, then you know one thing for sure: It is the <em>anti-virus software</em> that was causing the slow down! Please recognize that <em>we</em> can <strong>not</strong> fix this kind of problems. Instead, since the problem is actually a <em>defect</em> of the anti-virus software, please report the problem to the developer of the <em>anti-virus software</em>!</p>
<p>Another way of detecting performance issues caused by sloppy anti-virus software is monitoring the CPU usage in Task Manager (or <a href="https://technet.microsoft.com/en-us/sysinternals/bb896653.aspx"><em>Process Explorer</em></a>) while LameXP is starting up. Please make sure that you are <strong>not</strong> looking at the &quot;overall&quot; CPU usage, but at the CPU usage caused by the <em>individual</em> processes, and that &quot;show processes from all users&quot; is <em>enabled</em>. Then you will probably notice that <code>LameXP.exe</code> is sitting &quot;idle&quot;, more or less, while some <em>service process</em> belonging to the anti-virus software is &quot;hogging&quot; the CPU. A typical example looks like this:</p>
<p><img src="img/lamexp/av_gone_mad.png" alt="Figure" /></p>
<p>For reporting <em>performance issues</em>, please refer to anti-virus developer's web-site. Also, when reporting <em>performance issues</em>, please be self-confident: As a paying customer, you can demand that <em>performance issues</em> get fixed in a timely manner. Otherwise, get your money back!</p> <p>For reporting <em>performance issues</em>, please refer to anti-virus developer's web-site. Also, when reporting <em>performance issues</em>, please be self-confident: As a paying customer, you can demand that <em>performance issues</em> get fixed in a timely manner. Otherwise, get your money back!</p>
<h2 id="anti-virus-conclusions"><span class="header-section-number">3.3</span> Anti-Virus Conclusions</h2> <h2 id="anti-virus-conclusions"><span class="header-section-number">3.3</span> Anti-Virus Conclusions</h2>
<p>The <strong>code of conduct</strong> regarding problems and annoyances related to so-called &quot;anti-virus&quot; software:</p> <p>The <strong>code of conduct</strong> regarding problems and annoyances related to so-called &quot;anti-virus&quot; software:</p>

View File

@ -16,14 +16,13 @@ In addition to that, LameXP provides full support for *meta information*, includ
**Tier #1:** LameXP is currently being developed on the following platforms: **Tier #1:** LameXP is currently being developed on the following platforms:
* Microsoft Windows 8.1, 32-Bit and 64-Bit editions * Microsoft Windows 10, 32-Bit and 64-Bit editions
* Microsoft Windows 7 with Service Pack 1, 32-Bit and 64-Bit editions * Microsoft Windows 7 with Service Pack 1, 32-Bit and 64-Bit editions
* Microsoft Windows XP with Service Pack 3 **(see remarks)** * Microsoft Windows XP with Service Pack 3 **(see remarks)**
**Tier #2:** The following platforms should work too, but aren't tested extensively: **Tier #2:** The following platforms should work too, but aren't tested extensively:
* Microsoft Windows 10, 32-Bit and 64-Bit editions * Microsoft Windows 8.1, 32-Bit and 64-Bit editions
* Microsoft Windows 8.0, 32-Bit and 64-Bit editions * Microsoft Windows 8.0, 32-Bit and 64-Bit editions
* Microsoft Windows Vista with Service Pack 2, 32-Bit and 64-Bit editions * Microsoft Windows Vista with Service Pack 2, 32-Bit and 64-Bit editions
* Microsoft Windows XP x64 Edition with Service Pack 2 * Microsoft Windows XP x64 Edition with Service Pack 2
@ -142,7 +141,11 @@ At this point, it should be clear that implementing *workarounds* for defective
During the *startup procedure*, the LameXP software has to perform a number of *file-system* operations. This can take a few moments. However, the startup procedure should **never** take longer than *approximately* 5 seconds. Even on our test system &ndash; Windows 7 running on an *ancient* Intel Core2 processor with 4 GB of RAM &ndash; the startup procedure takes only about 1.5 seconds. And that is with the "real-time protection" of Microsoft Security Essentials (MSE) enabled! If we disable the MSE "real-time protection" feature, the startup procedure takes less than 0.5 seconds. *Unfortunately*, it has been brought to our attention, that some other anti-virus products may *slow down* the startup procedure significantly! Startup delays of up to 20 seconds have been reported by users, which corresponds to a slow down factor of **40&#xd7;** &ndash; caused by the anti-virus software! During the *startup procedure*, the LameXP software has to perform a number of *file-system* operations. This can take a few moments. However, the startup procedure should **never** take longer than *approximately* 5 seconds. Even on our test system &ndash; Windows 7 running on an *ancient* Intel Core2 processor with 4 GB of RAM &ndash; the startup procedure takes only about 1.5 seconds. And that is with the "real-time protection" of Microsoft Security Essentials (MSE) enabled! If we disable the MSE "real-time protection" feature, the startup procedure takes less than 0.5 seconds. *Unfortunately*, it has been brought to our attention, that some other anti-virus products may *slow down* the startup procedure significantly! Startup delays of up to 20 seconds have been reported by users, which corresponds to a slow down factor of **40&#xd7;** &ndash; caused by the anti-virus software!
Consequently, if you think that LameXP is starting up "slow" on your machine, we recommend to *temporarily* **disable** or **uninstall** your current anti-virus software. If your anti-virus software has a so-called "real-time protection" or "guard" feature, please be sure to *deactivate* that feature too! As soon as the anti-virus software has been *neutralized* and **no** longer affects legitimate applications, please try launching the LameXP software again. If it turns out that the startup procedure of LameXP has become significantly *faster* when the anti-virus software is **not** interfering, then you know one thing for sure: It is the *anti-virus software* that was causing the slow down! Please recognize that *we* can **not** fix this kind of problems. Instead, since the problem is actually a *defect* of the anti-virus software, please report the problem to the developer of the *anti-virus software*! Consequently, if you think that LameXP is starting up "slow" on your machine, we recommend to **temporarily** *disable* or *uninstall* your current anti-virus software. If your anti-virus software has a so-called "real-time protection" or "guard" feature, please be sure to *deactivate* that feature too! As soon as the anti-virus software has been *neutralized* and **no** longer affects legitimate applications, please try launching the LameXP software again. If it turns out that the startup procedure of LameXP has become significantly *faster* when the anti-virus software is **not** interfering, then you know one thing for sure: It is the *anti-virus software* that was causing the slow down! Please recognize that *we* can **not** fix this kind of problems. Instead, since the problem is actually a *defect* of the anti-virus software, please report the problem to the developer of the *anti-virus software*!
Another way of detecting performance issues caused by sloppy anti-virus software is monitoring the CPU usage in Task Manager (or [*Process Explorer*](https://technet.microsoft.com/en-us/sysinternals/bb896653.aspx)) while LameXP is starting up. Please make sure that you are **not** looking at the "overall" CPU usage, but at the CPU usage caused by the *individual* processes, and that "show processes from all users" is *enabled*. Then you will probably notice that `LameXP.exe` is sitting "idle", more or less, while some *service process* belonging to the anti-virus software is "hogging" the CPU. A typical example looks like this:
![Figure](img/lamexp/av_gone_mad.png)
For reporting *performance issues*, please refer to anti-virus developer's web-site. Also, when reporting *performance issues*, please be self-confident: As a paying customer, you can demand that *performance issues* get fixed in a timely manner. Otherwise, get your money back! For reporting *performance issues*, please refer to anti-virus developer's web-site. Also, when reporting *performance issues*, please be self-confident: As a paying customer, you can demand that *performance issues* get fixed in a timely manner. Otherwise, get your money back!

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -31,7 +31,7 @@
<context> <context>
<name>MainWindow</name> <name>MainWindow</name>
<message numerus="yes"> <message numerus="yes">
<location filename="../../src/Dialog_MainWindow.cpp" line="822"/> <location filename="../../src/Dialog_MainWindow.cpp" line="830"/>
<source>%n file(s) have been rejected, because read access was not granted!</source> <source>%n file(s) have been rejected, because read access was not granted!</source>
<translation> <translation>
<numerusform>%n file have been rejected, because read access was not granted!</numerusform> <numerusform>%n file have been rejected, because read access was not granted!</numerusform>
@ -39,7 +39,7 @@
</translation> </translation>
</message> </message>
<message numerus="yes"> <message numerus="yes">
<location filename="../../src/Dialog_MainWindow.cpp" line="826"/> <location filename="../../src/Dialog_MainWindow.cpp" line="834"/>
<source>%n file(s) have been rejected, because they are dummy CDDA files!</source> <source>%n file(s) have been rejected, because they are dummy CDDA files!</source>
<translation> <translation>
<numerusform>%n file have been rejected, because they are dummy CDDA files!</numerusform> <numerusform>%n file have been rejected, because they are dummy CDDA files!</numerusform>
@ -47,7 +47,7 @@
</translation> </translation>
</message> </message>
<message numerus="yes"> <message numerus="yes">
<location filename="../../src/Dialog_MainWindow.cpp" line="830"/> <location filename="../../src/Dialog_MainWindow.cpp" line="838"/>
<source>%n file(s) have been rejected, because they appear to be Cue Sheet images!</source> <source>%n file(s) have been rejected, because they appear to be Cue Sheet images!</source>
<translation> <translation>
<numerusform>%n file have been rejected, because they appear to be Cue Sheet images!</numerusform> <numerusform>%n file have been rejected, because they appear to be Cue Sheet images!</numerusform>
@ -55,7 +55,7 @@
</translation> </translation>
</message> </message>
<message numerus="yes"> <message numerus="yes">
<location filename="../../src/Dialog_MainWindow.cpp" line="834"/> <location filename="../../src/Dialog_MainWindow.cpp" line="842"/>
<source>%n file(s) have been rejected, because the file format could not be recognized!</source> <source>%n file(s) have been rejected, because the file format could not be recognized!</source>
<translation> <translation>
<numerusform>%n file have been rejected, because the file format could not be recognized!</numerusform> <numerusform>%n file have been rejected, because the file format could not be recognized!</numerusform>
@ -63,7 +63,7 @@
</translation> </translation>
</message> </message>
<message numerus="yes"> <message numerus="yes">
<location filename="../../src/Dialog_MainWindow.cpp" line="4220"/> <location filename="../../src/Dialog_MainWindow.cpp" line="4228"/>
<source>%n Instance(s)</source> <source>%n Instance(s)</source>
<translation> <translation>
<numerusform>%n Instance</numerusform> <numerusform>%n Instance</numerusform>

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

Binary file not shown.

View File

@ -35,7 +35,7 @@
#define VER_LAMEXP_MINOR_LO 2 #define VER_LAMEXP_MINOR_LO 2
#define VER_LAMEXP_TYPE Beta #define VER_LAMEXP_TYPE Beta
#define VER_LAMEXP_PATCH 4 #define VER_LAMEXP_PATCH 4
#define VER_LAMEXP_BUILD 1785 #define VER_LAMEXP_BUILD 1787
#define VER_LAMEXP_CONFG 1700 #define VER_LAMEXP_CONFG 1700
/////////////////////////////////////////////////////////////////////////////// ///////////////////////////////////////////////////////////////////////////////

View File

@ -129,9 +129,17 @@ while(0)
} \ } \
while(0) while(0)
#define LINK(URL) QString("<a href=\"%1\">%2</a>").arg(URL).arg(QString(URL).replace("-", "&minus;")) #define LINK(URL) \
#define FSLINK(PATH) QString("<a href=\"file:///%1\">%2</a>").arg(PATH).arg(QString(PATH).replace("-", "&minus;")) (QString("<a href=\"%1\">%2</a>").arg(URL).arg(QString(URL).replace("-", "&minus;")))
#define CENTER_CURRENT_OUTPUT_FOLDER_DELAYED QTimer::singleShot(125, this, SLOT(centerOutputFolderModel()))
#define LINK_EX(URL, NAME) \
(QString("<a href=\"%1\">%2</a>").arg(URL).arg(QString(NAME).replace("-", "&minus;")))
#define FSLINK(PATH) \
(QString("<a href=\"file:///%1\">%2</a>").arg(PATH).arg(QString(PATH).replace("-", "&minus;")))
#define CENTER_CURRENT_OUTPUT_FOLDER_DELAYED() \
QTimer::singleShot(125, this, SLOT(centerOutputFolderModel()))
//////////////////////////////////////////////////////////// ////////////////////////////////////////////////////////////
// Static Functions // Static Functions
@ -1477,7 +1485,7 @@ void MainWindow::windowShown(void)
{ {
QString message; QString message;
message += NOBR(tr("It seems that a bogus anti-virus software is slowing down the startup of LameXP.")).append("<br>"); message += NOBR(tr("It seems that a bogus anti-virus software is slowing down the startup of LameXP.")).append("<br>");
message += NOBR(tr("Please refer to the %1 document for details and solutions!")).arg("<a href=\"http://lamexp.sourceforge.net/doc/FAQ.html#df406578\">F.A.Q.</a>").append("<br>"); message += NOBR(tr("Please refer to the %1 document for details and solutions!")).arg(LINK_EX(QString("%1/Manual.html#performance-issues").arg(g_documents_base_url), tr("Manual"))).append("<br>");
if(QMessageBox::warning(this, tr("Slow Startup"), message, tr("Discard"), tr("Don't Show Again")) == 1) if(QMessageBox::warning(this, tr("Slow Startup"), message, tr("Discard"), tr("Don't Show Again")) == 1)
{ {
m_settings->antivirNotificationsEnabled(false); m_settings->antivirNotificationsEnabled(false);
@ -1861,7 +1869,7 @@ void MainWindow::tabPageChanged(int idx, const bool silent)
} }
else else
{ {
CENTER_CURRENT_OUTPUT_FOLDER_DELAYED; CENTER_CURRENT_OUTPUT_FOLDER_DELAYED();
} }
} }
@ -2908,7 +2916,7 @@ void MainWindow::gotoDesktopButtonClicked(void)
{ {
ui->outputFolderView->setCurrentIndex(m_fileSystemModel->index(desktopPath)); ui->outputFolderView->setCurrentIndex(m_fileSystemModel->index(desktopPath));
outputFolderViewClicked(ui->outputFolderView->currentIndex()); outputFolderViewClicked(ui->outputFolderView->currentIndex());
CENTER_CURRENT_OUTPUT_FOLDER_DELAYED; CENTER_CURRENT_OUTPUT_FOLDER_DELAYED();
} }
else else
{ {
@ -2933,7 +2941,7 @@ void MainWindow::gotoHomeFolderButtonClicked(void)
{ {
ui->outputFolderView->setCurrentIndex(m_fileSystemModel->index(homePath)); ui->outputFolderView->setCurrentIndex(m_fileSystemModel->index(homePath));
outputFolderViewClicked(ui->outputFolderView->currentIndex()); outputFolderViewClicked(ui->outputFolderView->currentIndex());
CENTER_CURRENT_OUTPUT_FOLDER_DELAYED; CENTER_CURRENT_OUTPUT_FOLDER_DELAYED();
} }
else else
{ {
@ -2958,7 +2966,7 @@ void MainWindow::gotoMusicFolderButtonClicked(void)
{ {
ui->outputFolderView->setCurrentIndex(m_fileSystemModel->index(musicPath)); ui->outputFolderView->setCurrentIndex(m_fileSystemModel->index(musicPath));
outputFolderViewClicked(ui->outputFolderView->currentIndex()); outputFolderViewClicked(ui->outputFolderView->currentIndex());
CENTER_CURRENT_OUTPUT_FOLDER_DELAYED; CENTER_CURRENT_OUTPUT_FOLDER_DELAYED();
} }
else else
{ {
@ -2986,7 +2994,7 @@ void MainWindow::gotoFavoriteFolder(void)
{ {
ui->outputFolderView->setCurrentIndex(m_fileSystemModel->index(path.canonicalPath())); ui->outputFolderView->setCurrentIndex(m_fileSystemModel->index(path.canonicalPath()));
outputFolderViewClicked(ui->outputFolderView->currentIndex()); outputFolderViewClicked(ui->outputFolderView->currentIndex());
CENTER_CURRENT_OUTPUT_FOLDER_DELAYED; CENTER_CURRENT_OUTPUT_FOLDER_DELAYED();
} }
else else
{ {
@ -3084,7 +3092,7 @@ void MainWindow::makeFolderButtonClicked(void)
QModelIndex newIndex = m_fileSystemModel->index(createdDir.canonicalPath()); QModelIndex newIndex = m_fileSystemModel->index(createdDir.canonicalPath());
ui->outputFolderView->setCurrentIndex(newIndex); ui->outputFolderView->setCurrentIndex(newIndex);
outputFolderViewClicked(newIndex); outputFolderViewClicked(newIndex);
CENTER_CURRENT_OUTPUT_FOLDER_DELAYED; CENTER_CURRENT_OUTPUT_FOLDER_DELAYED();
} }
} }
else else
@ -3170,7 +3178,7 @@ void MainWindow::goUpFolderContextActionTriggered(void)
{ {
MUtils::Sound::beep(MUtils::Sound::BEEP_WRN); MUtils::Sound::beep(MUtils::Sound::BEEP_WRN);
} }
CENTER_CURRENT_OUTPUT_FOLDER_DELAYED; CENTER_CURRENT_OUTPUT_FOLDER_DELAYED();
} }
} }
@ -3256,7 +3264,7 @@ void MainWindow::outputFolderEditFinished(void)
ui->outputFolderView->setEnabled(true); ui->outputFolderView->setEnabled(true);
if(!ok) MUtils::Sound::beep(MUtils::Sound::BEEP_ERR); if(!ok) MUtils::Sound::beep(MUtils::Sound::BEEP_ERR);
CENTER_CURRENT_OUTPUT_FOLDER_DELAYED; CENTER_CURRENT_OUTPUT_FOLDER_DELAYED();
} }
/* /*
@ -3295,7 +3303,7 @@ void MainWindow::initOutputFolderModel(void)
outputFolderViewClicked(ui->outputFolderView->currentIndex()); outputFolderViewClicked(ui->outputFolderView->currentIndex());
} }
CENTER_CURRENT_OUTPUT_FOLDER_DELAYED; CENTER_CURRENT_OUTPUT_FOLDER_DELAYED();
QTimer::singleShot(125, this, SLOT(initOutputFolderModel_doAsync())); QTimer::singleShot(125, this, SLOT(initOutputFolderModel_doAsync()));
} }
} }
@ -3350,7 +3358,7 @@ void MainWindow::outputFolderDirectoryLoaded(const QString &path)
{ {
if(m_outputFolderViewCentering) if(m_outputFolderViewCentering)
{ {
CENTER_CURRENT_OUTPUT_FOLDER_DELAYED; CENTER_CURRENT_OUTPUT_FOLDER_DELAYED();
} }
} }
@ -3361,7 +3369,7 @@ void MainWindow::outputFolderRowsInserted(const QModelIndex &parent, int start,
{ {
if(m_outputFolderViewCentering) if(m_outputFolderViewCentering)
{ {
CENTER_CURRENT_OUTPUT_FOLDER_DELAYED; CENTER_CURRENT_OUTPUT_FOLDER_DELAYED();
} }
} }