Search options (Page 7 of 21)

you may find it here,
https://git.tuxfamily.org/qet/qet.git/t … w.cpp#n195
it may also be that I am completely wrong

but even if you want to change this what should be the default function and how do you switch between

I think it is easy to adjust it manually, you will spend more time setting the automatic mode

in 0.8 place the part in the schematic again,
then QET will ask to adjust the others,
I thought this is how it works but this may have changed in the meantime.

Laurent,
see
https://qelectrotech.org/forum/viewtopic.php?id=1792
and
https://qelectrotech.org/forum/viewtopic.php?id=1804
I think it's time to make a blueprint of QET, what we want, how we want it, and then make it.
Laurent,understand, (I) can only make minor changes to the code, major changes require a plan.
Joshua has a plan I think, and I don't want to get in his way.
He's been fixing to many mistakes from me lately.
Yes, I read the git logs, and it's never nice to know that I m responsible for the bugs reported.

CVS?

https://www.vagabondjourney.com/what-is … o-stop-it/

-how big is your screen?
-fit's the diagram of qet on your screen or you have to scroll?
-elements list do you have to scroll?
or what do you think that causes this?

some info from the link:

Laurent, I think it's great that you've been keeping this up for years. I'll probably be crazy about all those simple questions.

time for an update

@ S.DEFFAUX
code:
https://git.tuxfamily.org/qet/qet.git/t … .cpp#n1769

void QETApp::configureQET()
{
    // determine the parent widget to use for the dialog
    // determine le widget parent a utiliser pour le dialogue
    QWidget *parent_widget = qApp->activeWindow();
 
    // create dialogue
    // cree le dialogue
    ConfigDialog cd;
    cd.setWindowTitle(tr("Configurer QElectroTech", "window title"));
    cd.setWindowModality(Qt::WindowModal);
    cd.addPage(new GeneralConfigurationPage());
    cd.addPage(new NewDiagramPage());
    cd.addPage(new ExportConfigPage());
    cd.addPage(new PrintConfigPage());
 
    // associates the dialog with a possible parent widget
    // associe le dialogue a un eventuel widget parent
    if (parent_widget) {
        cd.setParent(parent_widget, cd.windowFlags());
    }
 
    // display the dialog then avoid linking it to any parent widget
    // affiche le dialogue puis evite de le lier a un quelconque widget parent
    cd.exec();
    cd.setParent(nullptr, cd.windowFlags());
    qDebug() <<"configureQET"<<cd.size();
}

Debug: configureQET QSize(1400, 1000) (../../qet/sources/qetapp.cpp:1802, void QETApp::configureQET())

the 1000 is your problem, right?

Mod code:

if (parent_widget) {
        cd.setParent(parent_widget, cd.windowFlags());
    }

to

if (parent_widget) {
        cd.setParent(parent_widget, cd.windowFlags());
        cd.resize(parent_widget->size());
    }

Debug: configureQET QSize(1280, 720) (../../qet/sources/qetapp.cpp:1803, void QETApp::configureQET())

but this is a problem for large screens.

if (parent_widget) {
        cd.setParent(parent_widget, cd.windowFlags());
        cd.setMaximumSize(parent_widget->size());
    }

is ok

https://git.tuxfamily.org/qet/qet.git/c … f343adb020

I ran the Clang-Tidy tool on qet ... umm there are still a lot of improvements to be done.

Adding

// NOLINT

will also be needed in the code
suppressing undesired diagnostics
extra info
Memcheck also makes some comments.

Laurent,
where does the "git6826." come from?
And how do you link this to the git ID SHA?

https://qelectrotech.org/wiki_new/doc/p … tu_windows

ok thanks Joshua and Laurent  for the info, there is a solution for "KColorButton" I think, for KAutoSaveFile I will look further.
And for git submodules is it allowed or not?