c'est possible
diagram.cpp:2160

/**
    @brief Diagram::adjustSceneRect
    Recalcul and adjust the size of the scene
*/

void Diagram::adjustSceneRect()
{
    QRectF old_rect = sceneRect();
    setSceneRect(border_and_titleblock.borderAndTitleBlockRect().united(
                 itemsBoundingRect()));
    update(old_rect.united(sceneRect()));
}

277

(60 replies, posted in Code)

sources/elementtextpattern.h:       Copyright 2006-2020 The QElectroTech Team
sources/elementtextsmover.cpp:      Copyright 2006-2012 Xavier Guerrin
sources/elementtextsmover.h:        Copyright 2006-2012 Xavier Guerrin

should this stay?

mmm... headers

/sources/bordertitleblock.cpp:30

#define MIN_COLUMN_COUNT 0
#define MIN_ROW_COUNT 0
#define MIN_COLUMN_WIDTH 1.0
#define MIN_ROW_HEIGHT 1.0

279

(60 replies, posted in Code)

> sudo which lspci
[sudo] wachtwoord voor root: 
/sbin/lspci

280

(60 replies, posted in Code)

De-Backer wrote:

Note: some OS requires root rights.

> lspci | grep VGA | cut -d : -f 3
lspci: opdracht niet gevonden
> sudo lspci | grep VGA | cut -d : -f 3
[sudo] wachtwoord voor root: 
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1)
> 

et encore une fois c'est déjà bien caché à nouveau, cela peut prendre un certain temps

peut-être mais alors nous ne courons pas dans la grille?

283

(60 replies, posted in Code)

Note: some OS requires root rights.

scorpio810 wrote:

Joshua takes advantage of his vacation to do work on his house.
He doesn't turn on his PC much, from what he told me yesterday.

Thanks for informing me.
I will work on the debugger in the meantime.
There are still many things to do besides terminal name.

scorpio 810, joshua and martin did you get my email?

scorpio810 aren't you going too fast? we have not yet decided where to place the terminal name in the project file and what it looks like.

Let me explain the problem.
- Yes the code available can already provide the functionality. (branch dev_Terminal_name)
The problem:

Joshua wrote:

Martin work on a harness feature and if I remember well add terminal number.

They were all in the making of functionality, in a way I don't know yet.
If I now romel there, this will cause problems for the other features.

In short, if you make changes to the XML structure then all developers must know and agree to it.
And that's why it's still not in the master branch.

288

(16 replies, posted in EN : Help, suggestions, discussions, ...)

scorpio810 wrote:

No, I compile MXE Qt cross-env in static mode for Windows packages, libs, etc, .

I didn't know you can do that, given the license of qt. O_O

289

(65 replies, posted in Code)

looks nice,

I have a Custom Process Step when Building QElectroTech :

doxygen Doxyfile

gives me a lot of error messages of doxygen.

i will do my best to resolve these.

290

(0 replies, posted in Code)

wiki
qelectrotech
dev / pre

questions:
- where is the XML Schema in .qet file?
- if there is any info missing / wrong in the wiki let me know

note: the wiki is not ready yet

I think this summed it up:
https://geekandpoke.typepad.com/.a/6a00d8341d3df553ef0168eabe2192970c-pi

OK, enough laughs (but it is sometimes necessary), I'll move on to the doc first.
In the meantime I may be able to learn something.

292

(16 replies, posted in EN : Help, suggestions, discussions, ...)

you can give this a try?
https://download.qelectrotech.org/qet/b … 0-08-07-1/

Test writeToFile on a other Thread
   
    to improve this for windows performance

Joshua wrote:

Martin work on a harness feature and if I remember well add terminal number.

Is it the intention to be able to do this?
https://www.youtube.com/watch?v=vWnTZy1gbxw

<conductor vertirotatetext="270" terminal1="{5455d1e1-4acb-47dd-8fcf-cb38fc88094a}" bicolor="true" element1="{01ef1122-8b93-40cd-bbb7-1e57eec47854}" dash-size="2" x="0" text_color="#000000" numsize="7" conductor_color="" horizontal-alignment="AlignBottom" displaytext="1" tension_protocol="" element2="{32ce3522-370f-42f3-99ae-dbb703d01767}" conductor_section="" vertical-alignment="AlignRight" freezeLabel="false" num="_" onetextperfolio="1" condsize="1" color2="#ff0000" function="" type="multi" horizrotatetext="0" terminal2="{93173c01-5706-498d-ab28-9fdb3dfe1a69}" formula="" y="0">
                <sequentialNumbers/>
            </conductor>

terminal1 in element collection:

<terminal name="13" x="40" y="-30" uuid="{5455d1e1-4acb-47dd-8fcf-cb38fc88094a}" orientation="n"/>

of element1 in diagram

<element prefix="" x="460" y="390" z="10" uuid="{01ef1122-8b93-40cd-bbb7-1e57eec47854}" freezeLabel="false" type="embed://import/test_element.elmt" orientation="0">
                <terminals>
                    <terminal number="_" nameHidden="0" name="11" x="0" y="-26" orientation="0" id="6"/>
                    <terminal number="_" nameHidden="0" name="12" x="20" y="-26" orientation="0" id="7"/>
                    <terminal number="_" nameHidden="0" name="13" x="40" y="-26" orientation="0" id="8"/>
                    <terminal number="_" nameHidden="0" name="21" x="0" y="26" orientation="2" id="9"/>
                    <terminal number="_" nameHidden="0" name="22" x="20" y="26" orientation="2" id="10"/>
                    <terminal number="_" nameHidden="0" name="23" x="40" y="26" orientation="2" id="11"/>
                </terminals>
                <inputs/>
                <dynamic_texts>
                    <dynamic_elmt_text text_width="-1" font="Sans Serif,9,-1,5,0,0,0,0,0,0,normal" rotation="0" Valignment="AlignTop" x="-25" y="-5" frame="false" text_from="UserText" uuid="{4828408a-9bca-4f1b-966f-089539358e21}" Halignment="AlignLeft">
                        <text>_</text>
                    </dynamic_elmt_text>
                </dynamic_texts>
                <texts_groups/>
            </element>

to element2 in diagram

<element prefix="" x="460" y="290" z="10" uuid="{32ce3522-370f-42f3-99ae-dbb703d01767}" freezeLabel="false" type="embed://import/test_element.elmt" orientation="0">
                <terminals>
                    <terminal number="_" nameHidden="0" name="11" x="0" y="-26" orientation="0" id="0"/>
                    <terminal number="_" nameHidden="0" name="12" x="20" y="-26" orientation="0" id="1"/>
                    <terminal number="_" nameHidden="0" name="13" x="40" y="-26" orientation="0" id="2"/>
                    <terminal number="_" nameHidden="0" name="21" x="0" y="26" orientation="2" id="3"/>
                    <terminal number="_" nameHidden="0" name="22" x="20" y="26" orientation="2" id="4"/>
                    <terminal number="_" nameHidden="0" name="23" x="40" y="26" orientation="2" id="5"/>
                </terminals>
                <inputs/>
                <dynamic_texts>
                    <dynamic_elmt_text text_width="-1" font="Sans Serif,9,-1,5,0,0,0,0,0,0,normal" rotation="0" Valignment="AlignTop" x="-25" y="-5" frame="false" text_from="UserText" uuid="{24031ee2-36f3-4a95-80a9-eaf09479d2ef}" Halignment="AlignLeft">
                        <text>_</text>
                    </dynamic_elmt_text>
                </dynamic_texts>
                <texts_groups/>
            </element>

terminal2 in element collection::

<terminal name="23" x="40" y="30" uuid="{93173c01-5706-498d-ab28-9fdb3dfe1a69}" orientation="s"/>

------------------------------------------

<terminal number="_" nameHidden="0" name="11" x="0" y="-26" orientation="0" id="6"/>

is unnecessary in diagram

the link is
element1 in diagram
element2 in diagram
terminal1 in element collection
terminal2 in element collection

conductor in diagram => makes the connection (uuid)

in short:

if the terminal have a name in element collection then we can make the list.
Or am I wrong?

De-Backer wrote:

in test_element.elmt

<terminal x="0" uuid="{a9f1a07f-2a4a-460a-b6e7-d831f73e1a08}" name="21" orientation="s" y="30"/>
<terminal x="40" uuid="{93173c01-5706-498d-ab28-9fdb3dfe1a69}" name="23" orientation="s" y="30"/>
<terminal x="0" uuid="{1e57863e-e456-430b-a204-6831722b7312}" name="11" orientation="n" y="-30"/>
<terminal x="20" uuid="{42dd9184-b750-4ae3-8e89-593c958526f4}" name="12" orientation="n" y="-30"/>
<terminal x="20" uuid="{3dc51ac8-c354-499d-8c3b-f46ff6e435ad}" name="22" orientation="s" y="30"/>
<terminal x="40" uuid="{5455d1e1-4acb-47dd-8fcf-cb38fc88094a}" name="13" orientation="n" y="-30"/>

works
but in test.qet

diagram
<terminal x="0" id="0" nameHidden="0" orientation="0" name="_" number="_" y="-26"/>
<terminal x="20" id="1" nameHidden="0" orientation="0" name="_" number="_" y="-26"/>
<terminal x="40" id="2" nameHidden="0" orientation="0" name="_" number="_" y="-26"/>
<terminal x="0" id="3" nameHidden="0" orientation="2" name="_" number="_" y="26"/>
<terminal x="20" id="4" nameHidden="0" orientation="2" name="_" number="_" y="26"/>
<terminal x="40" id="5" nameHidden="0" orientation="2" name="_" number="_" y="26"/>

I search through it.

terminal.cpp @ init("_", "_", false);
=>name="_" number="_"

Terminal::Terminal(TerminalData* data, Element* e) :
    QGraphicsObject(e),
    d(data),
    parent_element_(e)
{
    // TODO: what is when multiple parents exist. So the other relation is lost.
    d->setParent(this);
    init("_", "_", false);
}

1 step further (name)

diagram
<terminals>
                    <terminal number="_" nameHidden="0" name="11" x="0" y="-26" orientation="0" id="0"/>
                    <terminal number="_" nameHidden="0" name="12" x="20" y="-26" orientation="0" id="1"/>
                    <terminal number="_" nameHidden="0" name="13" x="40" y="-26" orientation="0" id="2"/>
                    <terminal number="_" nameHidden="0" name="21" x="0" y="26" orientation="2" id="3"/>
                    <terminal number="_" nameHidden="0" name="22" x="20" y="26" orientation="2" id="4"/>
                    <terminal number="_" nameHidden="0" name="23" x="40" y="26" orientation="2" id="5"/>
                </terminals>

My question to @Joshua: what should it look like if you start from scratch?
And why don't you want to do this. (2 different files should not be supported, just convert to the new format.)
I know this will take a long time.
But then you work on a structure that you have made yourself, one that can be less difficult.
we can then also change the element lib.

(This is a question in the what if)

palhenrique wrote:

1st. thank you so much for your time.
2nd. That's how I use automatic numbering. When I close the project and then open it, the numbering disappears. % Seqh_1 appears instead of the number.
3rd. When I change the status of the project to completed, nothing happens. Should I replace the formula by number only !?

1st. no problem
2nd. When I close the project and then open it, the numbering is still there. ( windows vs linux ??  no, can you start QElectroTech in the CMD and see if there are any errors?)
3rd. I do not know.

an example:
https://youtu.be/jFJBnJqbC3Q =>Delete

QElectroTech V 0.80-DEV
Compilation: GCC 9.3.1 20200406 [revision 6db837a5288ee3ca5ec504fbd5a765817e556ac2]
Built with Qt 5.14.1 - Date : May 26 2020 : 21:18:03 
Run with Qt 5.15.0 using 16 thread(s)
OS : linux - x86_64 - Version : openSUSE Tumbleweed - Kernel : 5.7.11-1-default

scorpio810 wrote:

I sent you a few emails, then you will better understand Martin's desired goal.
It is a continuation of a very old work to add numbers or text properties on terminals primitives:
https://listengine.tuxfamily.org/lists. … 00034.html

thanks,

Joshua wrote:

Very wrong approch (if I were to create it now I will use uuid instead).

but he does not explain why.
further they talk about the wires and no longer about the terminals.
Am I right so far?

my thought:

part        designation  code diagram   code element
element   = K01          ??             UUID
terminal  = 11           ??             11
wire      = 10 200       ??             ------does not exist
terminal  = 22           ??             22
element   = K05          ??             UUID

??= will this be a new unique ID (UUID)?

scorpio810 wrote:
Aleksandr wrote:

I also faced this problem. It turned out that when creating elements, you cannot copy outputs. Each output gets its own ID. And when copying, all pins have the same ID. I found out about this when I opened the element in a text editor.

Thanks for feedback Aleksandr.

UUID for terminals output was added recently by Martin for new feature and yes is a bug, thanks.
https://qelectrotech.org/forum/viewtopi … 055#p12055
When pasting terminals on editor, editor need to create a new random UUID and not copy the parent UUID property.

Maybe a workaround is to remove UUID on XML <terminal orientation=               > attributes chain.

Editing an element linked to wires is risky if you move the terminals a little too much in editor.

Who will try to solve this?
And how, the copy paste is not designed to handle this.

copy() {
    // delegue cette action a la scene
    m_scene -> copy();
    offset_paste_count_ = 0;
}
paste(const QDomDocument &xml_document, const QPointF &pos) {
    // objet pour recuperer le contenu ajoute au schema par le coller
    ElementContent content_pasted;
    m_scene -> fromXml(xml_document, pos, false, &content_pasted);
 
    // si quelque chose a effectivement ete ajoute au schema, on cree un objet d'annulation
    if (content_pasted.count()) {
        m_scene -> clearSelection();
        PastePartsCommand *undo_object = new PastePartsCommand(this, content_pasted);
        m_scene -> undoStack().push(undo_object);
    }
    return(content_pasted);
}

maybe one should explaining me the utility / purpose for UUID terminals,
what was wrong with 1 UUID for the element,
and numbers for the terminals?

02going_arrow.elmt (version=0.3)

<definition width="40" version="0.3" hotspot_x="18" hotspot_y="15" height="30" type="element" ic="true" orientation="dyyy"
link_type="next_report">
<uuid uuid="{717352A1-F3C7-49C7-9A06-51620AB5CA00}"/><names>
        <name lang="ru">Следующая страница</name>
        <name lang="ar">الصفحة التالية</name>
        <name lang="de">Nächste Folie</name>
        <name lang="el">Επόμενη σελίδα</name>
        <name lang="en">Going arrow</name>
        <name lang="it">Foglio successivo</name>
        <name lang="fr">Folio suivant</name>
        <name lang="pl">Wyjście adresowe</name>
        <name lang="es">Folio siguiente</name>
        <name lang="cs">Další list</name>
        <name lang="nl">Referentie volgend</name>
    </names>
    <informations>Author: The QElectroTech team
License: see http://qelectrotech.org/wiki/doc/elements_license</informations>
    <description>
        <polygon x4="-9" antialias="true" style="line-style:normal;line-weight:normal;filling:black;color:black" closed="false" y1="-4" x1="-9" y2="4" x2="-9" y3="0" x3="2" y4="-4"/>
        <line length1="1.5" length2="1.5" antialias="false" end1="none" end2="none" style="line-style:normal;line-weight:normal;filling:none;color:black" y1="0" x1="-9" y2="0" x2="-12"/>
        <input x="6" y="0" size="9" rotate="true" text="/"/>
        <terminal x="-13" y="0" nameHidden="0" number="" name="" orientation="w"/>
    </description>
</definition>

version="0.80"

<definition link_type="previous_report" hotspot_x="8" type="element" width="30" hotspot_y="10" height="20" version="0.80" orientation="dyyy">
    <uuid uuid="{d9d5ac46-d734-49f6-9027-ed5a50e4547d}"/>
    <names>
        <name lang="es">folio anterior</name>
        <name lang="nl">Referentie Vorig</name>
        <name lang="it">Foglio precedente</name>
        <name lang="de">Vorherige Folie</name>
        <name lang="ru">Предыдущая страница</name>
        <name lang="ar">الصفحة السابقة</name>
        <name lang="el">Προηγούμενη σελίδα</name>
        <name lang="pl">Wejście adresowe</name>
        <name lang="en">Coming arrow</name>
        <name lang="fr">Folio précédent</name>
        <name lang="cs">Předchozí list</name>
    </names>
    <informations>Author: The QElectroTech team
License: see http://qelectrotech.org/wiki/doc/elements_license</informations>
    <description>
        <polygon x1="-1" y2="4" x4="-1" x2="-1" style="line-style:normal;line-weight:normal;filling:black;color:black" y4="-4" y1="-4" antialias="true" x3="9" y3="0" closed="false"/>
        <line x1="9" y2="0" end1="none" length2="1.5" x2="12" end2="none" style="line-style:normal;line-weight:normal;filling:none;color:black" length1="1.5" y1="0" antialias="false"/>
        <dynamic_text text_from="UserText" Valignment="AlignTop" z="3" text_width="-1" font="Sans Serif,9,-1,5,50,0,0,0,0,0" x="-44" uuid="{8b32ab87-b8ec-4564-bdec-c3ea4036a492}" y="-11.5" Halignment="AlignLeft" frame="false" rotation="0">
            <text>/</text>
        </dynamic_text>
        <terminal name="" x="13" uuid="{6db93440-be5c-4e83-bae3-34a68cb24127}" y="0" orientation="e"/>
    </description>
</definition>

for KiCAD;
connector.lib
(terminal = X) no UUID id's not even for the element

#
# 4P2C
#
DEF 4P2C J 0 40 Y Y 1 F N
F0 "J" -200 350 50 H V R CNN
F1 "4P2C" 100 350 50 H V L CNN
F2 "" 0 50 50 V I C CNN
F3 "" 0 50 50 V I C CNN
$FPLIST
 4P2C*
$ENDFPLIST
DRAW
S 300 300 -300 -200 0 1 10 f
P 3 0 1 0 -250 -25 -200 -25 -200 -25 N
P 3 0 1 0 -250 25 -200 25 -200 25 N
P 3 0 1 0 -250 75 -200 75 -200 75 N
P 3 0 1 0 -250 125 -200 125 -200 125 N
P 15 0 1 0 -250 -125 -250 225 -50 225 150 225 150 175 200 175 200 125 250 125 250 -25 200 -25 200 -75 150 -75 150 -125 -250 -125 -250 -125 N
X ~ 1 400 0 100 L 50 50 1 1 P
X ~ 2 400 100 100 L 50 50 1 1 P
ENDDRAW
ENDDEF

connector.dcm

#
$CMP 4P2C
D RJ connector, 4P2C (4 positions 2 connected)
K 4P2C RJ female connector
F ~
$ENDCMP