CactiChameleon9/PrismLauncher
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
064ae49d2b
PrismLauncher/launcher/ui/widgets/InfoFrame.cpp

173 lines
3.9 KiB
C++
Raw Normal View History

NOISSUE Update Copyright Year
2021-01-18 07:28:54 +00:00
/* Copyright 2013-2021 MultiMC Contributors
Licenses, cleanup
2013-10-08 22:11:24 +01:00
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
switch from tooltip to messagebox
2013-10-12 14:19:49 +01:00
#include <QMessageBox>
Reformat and (slightly) decruft all the things.
2013-11-04 01:53:05 +00:00
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
#include "InfoFrame.h"
#include "ui_InfoFrame.h"
NOISSUE continue reshuffling the codebase
2021-11-22 02:55:16 +00:00
#include "ui/dialogs/CustomMessageBox.h"
Reformat and (slightly) decruft all the things.
2013-11-04 01:53:05 +00:00
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
InfoFrame::InfoFrame(QWidget *parent) :
QFrame(parent),
ui(new Ui::InfoFrame)
{
ui->setupUi(this);
ui->descriptionLabel->setHidden(true);
ui->nameLabel->setHidden(true);
updateHiddenState();
}
InfoFrame::~InfoFrame()
{
delete ui;
}
void InfoFrame::updateWithMod(Mod const& m)
Move mod info frame and handler to MCModInfoFrame, use on all instances
2013-10-08 21:45:48 +01:00
{
refactor: move general info from Mod to Resource This allows us to create other resources that are not Mods, but can still share a significant portion of code. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-09 05:53:50 +01:00
if (m.type() == ResourceType::FOLDER)
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
{
clear();
return;
}
Show defaults if mod type is 'folder'
2013-10-08 22:25:56 +01:00
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
QString text = "";
QString name = "";
if (m.name().isEmpty())
refactor: remove unused mod info and organize some stuff
2022-04-16 02:07:35 +01:00
name = m.internal_id();
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
else
name = m.name();
Fall back to mod ID if name is missing for some reason
2013-10-09 03:10:56 +01:00
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
if (m.homeurl().isEmpty())
text = name;
else
text = "<a href=\"" + m.homeurl() + "\">" + name + "</a>";
if (!m.authors().isEmpty())
NOISSUE refactor Mod a bunch, get rid of dead code
2019-08-03 04:30:46 +01:00
text += " by " + m.authors().join(", ");
Move mod info frame and handler to MCModInfoFrame, use on all instances
2013-10-08 21:45:48 +01:00
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
setName(text);
Move mod info frame and handler to MCModInfoFrame, use on all instances
2013-10-08 21:45:48 +01:00
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
if (m.description().isEmpty())
{
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
setDescription(QString());
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
}
else
{
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
setDescription(m.description());
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
}
Mod info, with less HTML! And responding to keyboard events too.
2013-10-09 01:03:02 +01:00
}
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
void InfoFrame::updateWithResource(const Resource& resource)
Move mod info frame and handler to MCModInfoFrame, use on all instances
2013-10-08 21:45:48 +01:00
{
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
setName(resource.name());
Move mod info frame and handler to MCModInfoFrame, use on all instances
2013-10-08 21:45:48 +01:00
}
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
void InfoFrame::clear()
Move mod info frame and handler to MCModInfoFrame, use on all instances
2013-10-08 21:45:48 +01:00
{
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
setName();
setDescription();
Move mod info frame and handler to MCModInfoFrame, use on all instances
2013-10-08 21:45:48 +01:00
}
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
void InfoFrame::updateHiddenState()
GH-1313 remove translatable strings from MCModInfoFrame
2016-01-02 03:01:00 +00:00
{
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
if(ui->descriptionLabel->isHidden() && ui->nameLabel->isHidden())
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
{
setHidden(true);
}
else
{
setHidden(false);
}
GH-1313 remove translatable strings from MCModInfoFrame
2016-01-02 03:01:00 +00:00
}
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
void InfoFrame::setName(QString text)
Move mod info frame and handler to MCModInfoFrame, use on all instances
2013-10-08 21:45:48 +01:00
{
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
if(text.isEmpty())
{
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
ui->nameLabel->setHidden(true);
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
}
else
{
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
ui->nameLabel->setText(text);
ui->nameLabel->setHidden(false);
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
}
updateHiddenState();
Move mod info frame and handler to MCModInfoFrame, use on all instances
2013-10-08 21:45:48 +01:00
}
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
void InfoFrame::setDescription(QString text)
Move mod info frame and handler to MCModInfoFrame, use on all instances
2013-10-08 21:45:48 +01:00
{
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
if(text.isEmpty())
{
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
ui->descriptionLabel->setHidden(true);
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
updateHiddenState();
return;
}
else
{
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
ui->descriptionLabel->setHidden(false);
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
updateHiddenState();
}
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
ui->descriptionLabel->setToolTip("");
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
QString intermediatetext = text.trimmed();
bool prev(false);
QChar rem('\n');
QString finaltext;
finaltext.reserve(intermediatetext.size());
foreach(const QChar& c, intermediatetext)
{
if(c == rem && prev){
continue;
}
prev = c == rem;
finaltext += c;
}
QString labeltext;
labeltext.reserve(300);
if(finaltext.length() > 290)
{
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
ui->descriptionLabel->setOpenExternalLinks(false);
ui->descriptionLabel->setTextFormat(Qt::TextFormat::RichText);
m_description = text;
NOISSUE Add pack author and description to technic modpack import page
2020-11-02 21:28:07 +00:00
// This allows injecting HTML here.
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
labeltext.append("<html><body>" + finaltext.left(287) + "<a href=\"#mod_desc\">...</a></body></html>");
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
QObject::connect(ui->descriptionLabel, &QLabel::linkActivated, this, &InfoFrame::descriptionEllipsisHandler);
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
}
else
{
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
ui->descriptionLabel->setTextFormat(Qt::TextFormat::PlainText);
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
labeltext.append(finaltext);
}
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
ui->descriptionLabel->setText(labeltext);
Move mod info frame and handler to MCModInfoFrame, use on all instances
2013-10-08 21:45:48 +01:00
}
GH-1322 fix mod description ... button popping up multiple dialogs
2015-11-12 23:50:38 +00:00
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
void InfoFrame::descriptionEllipsisHandler(QString link)
switch from tooltip to messagebox
2013-10-12 14:19:49 +01:00
{
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
if(!m_current_box)
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
{
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
m_current_box = CustomMessageBox::selectable(this, "", m_description);
connect(m_current_box, &QMessageBox::finished, this, &InfoFrame::boxClosed);
m_current_box->show();
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
}
else
{
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
m_current_box->setText(m_description);
NOISSUE tabs -> spaces
2018-07-15 13:51:05 +01:00
}
GH-1322 fix mod description ... button popping up multiple dialogs
2015-11-12 23:50:38 +00:00
}
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
void InfoFrame::boxClosed(int result)
GH-1322 fix mod description ... button popping up multiple dialogs
2015-11-12 23:50:38 +00:00
{
refactor: adapt rest of the codebase to the new resource model In order to access the ModFolderModel from the ModFolderPage, i created a new m_model for the correct type, shadowing the m_model of type ResourceFolderModel. This creates two shared_ptr references to the same object, but since they will have the same lifetime, it doesn't generate a memory leak. Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-10 18:48:34 +01:00
m_current_box = nullptr;
switch from tooltip to messagebox
2013-10-12 14:19:49 +01:00
}
Reference in New Issue Copy Permalink