51 Reply by plc-user

(6 replies, posted in FR : Aide, suggestions, discussions, ...)

Did you read this Thread / Post ?
https://qelectrotech.org/forum/viewtopi … 857#p19857

Go to forum: FR : Aide, suggestions, discussions, ...

52 Reply by plc-user

(3 replies, posted in FR : Aide, suggestions, discussions, ...)

Salut oc67 !

Vielleicht nicht ganz die Antwort, die Du erhofft hast, aber:
Hast Du schon hier gelesen?
https://qelectrotech.org/forum/viewtopi … 438#p18438

Go to forum: FR : Aide, suggestions, discussions, ...

53 Reply by plc-user

(26 replies, posted in FR : Aide, suggestions, discussions, ...)

Salut Laurent !

Thanks for the links to the source code!

In my programme I already have all the information available that makes up a connection. That includes all information about the connected elements. The challenge I see at the moment is figuring out the logic of which connection I need to change and how, in order to be able to delete another connection.

From the file "Verweis.qet":
The PE connection can be deleted without any substitution, because on the one side there is a component (X0.PE) connected, but on the other side of the connection there is only a reference that does not point anywhere and also has no second connection.

The situation is different with the " Nonsense" line:
From X1:2, a connection goes to the left to the link that points nowhere. However, the line must not be deleted because a second connection is attached to the left reference, which goes somewhere. I therefore have to transfer the data from the second connection to the connection to X1:2 in order to be able to delete one of the two connections.
You have to move from point to point in order to delete as many connections as possible. Ideally, no reference element will remain at the end.

The situation is similar for the "Phase" and "Null" connections, which go from X0 to K1 and K2.

Go to forum: FR : Aide, suggestions, discussions, ...

54 Reply by plc-user

(26 replies, posted in FR : Aide, suggestions, discussions, ...)

Salut Laurent !

scorpio810 wrote:

good job. nomicons/wink

What program you use for that?

Thank you!  nomicons/smile

As already said, I take this as a programming-exercise in C++.
And:
The future goal has to be, that this code may be included in QET...!

Go to forum: FR : Aide, suggestions, discussions, ...

55 Reply by plc-user

(26 replies, posted in FR : Aide, suggestions, discussions, ...)

Hello everyone!

In my previous posts only raw data was shown as output. That can be a little confusing...

The programming exercise has continued and now the output is a little clearer. I have now attached a screenshot of LibreOffice Calc in which the unprocessed connections from the file "Verweise.qet" are listed at the top. I have assigned a few names and labels before. Some designations of terminal blocks are still missing, but I think you can see, what's the plan...

In the lower half, I have inserted a manually edited list of how I imagine a cable plan should be automatically reduced from the raw data.

The requirement for this is that all terminals of all elements used in the QET-file are provided with UUIDs and names! Only then, in my opinion, can such a list be automatically generated and meaningfully reduced.

Go to forum: FR : Aide, suggestions, discussions, ...

56 Reply by plc-user

(26 replies, posted in FR : Aide, suggestions, discussions, ...)

Salut Laurent !

As already written, this is a nice programming exercise. nomicons/wink
I already have a list of connections, where the terminals can access all information of the connected element.

In addition, it is a bit of a challenge to create a list that reduces the number of connections in such a sensible way that only those remain where a wire can really be connected! In the example "Verweise.qet": Reduce from 13 to 6 connections.

Such a list can certainly help the electrician: He then doesn't have to flip through the pages of a wiring diagram a lot to determine the second side of the wire. The wire properties (cross-section, color, etc.) are also not included in the circuit diagram for every connection...

Go to forum: FR : Aide, suggestions, discussions, ...

57 Reply by plc-user

(1 replies, posted in Elements)

Hello brutaldeath!

brutaldeath wrote:

Do not hesitate to answer for adjustement nomicons/wink

In my opinion:
Elements with so many terminals should be divided into several function groups and then added to the collection as master/slave elements.
For another case, I once suggested something like this from the appendix. The slave components are only roughly sketched and still need to be reworked, but that's roughly what I mean.
The manufacturer, designation and label for the slaves are dynamic texts that are filled from master-info, when connected.

[Edited]
And when it comes to automatic generation of cable-plans (https://qelectrotech.org/forum/viewtopic.php?id=2764):
The terminals need to have names.

You asked for feedback!  nomicons/wink

Best regards
  plc-user

Go to forum: Elements

58 Reply by plc-user

(26 replies, posted in FR : Aide, suggestions, discussions, ...)

Salut Laurent !

In my opinion, we should not add so much information to the connections that is already in the QET file for the elements anyway. This only unnecessarily bloates the file...
And it doesn't make the biggest problem any easier: connections with coming and going references.

I have attached a file that shows at least some of the problem cases. It looks quite simple at first glance, but as I said, it's not trivial! Take a look at the connections in the QET file: So many connections in the QET file, but only six wires that can be connected. These have to be sorted out automatically!

Just to clarify what the original task is:
We want to create a wiring diagram, or rather a text-based wiring list, for the electrician so that he can see which wire he has to pull from where to where, isn't it? For example:
"Pull a 1.5mm² green wire from K1 terminal A1 to lamp H1 terminal 2."
References are no terminal points to which wires can be connected...

Go to forum: FR : Aide, suggestions, discussions, ...

59 Reply by plc-user

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

nbeachey wrote:

Is there a setting I'm missing so that they don't interfere with each other?

As far as I know: No.

nbeachey wrote:

Also, I'm not finding much information on whatever "Organ of Protection" means.

Protective device such as circuit breakers, which can also have auxiliary contacts.

Go to forum: EN : Help, suggestions, discussions, ...

60 Reply by plc-user

(26 replies, posted in FR : Aide, suggestions, discussions, ...)

Salut Laurent !

As a programming exercise, I wrote a small program that extracts the elements and conductors from a QET file. In addition, the master/slave assignments are already made so that the properties of the master (label, etc.) also appear for the slave elements in the list of elements and conductors.
The real challenge, however, is (as already mentioned) the cross-folio wiring!
As can be seen in the code-windows below, for some connections the lines from one element go "to nowhere". These are the going/coming arrows.
I have used your examples as a QET file and extended some of them.

Remark:
In the code-windows below there are some line-breaks inserted automatically. To view the "real" lines, copy the content to a text-editor.

---------------
QET-Projekt     : Title: test_terminal_name | FileName: untitled2 | FilePath: /media/backup6/download/untitled2.qet | SaveDate: 19/06/2024 | SaveTime: 12:12
Anzahl Diagramme: 1
Anzahl Elemente : 5
Anzahl Leiter   : 3
---------------
  Element: Type: embed://import/10_electric/10_allpole/310_relays_contactors_contacts/02_contacts_cross_referencing/01_auxiliary_contacts/con_simple.elmt | UUID: {f253c71e-38a7-4155-8ab4-a844ced1a227} | Manufacturer:  | Description:  | Designation:  | Label: KA1 | Link_Type: slave | Linked with: {0a20780e-16b6-4198-b487-a0a22c37b1a0}
  Element: Type: embed://import/10_electric/10_allpole/310_relays_contactors_contacts/01_coils/bobine3.elmt | UUID: {0a20780e-16b6-4198-b487-a0a22c37b1a0} | Manufacturer:  | Description:  | Designation:  | Label: KA1 | Link_Type: master | Linked with: {f253c71e-38a7-4155-8ab4-a844ced1a227}
  Element: Type: embed://import/10_electric/10_allpole/100_folio_referencing/02going_arrow.elmt | UUID: {2de121e3-fb78-48a4-8f9a-bfee50276de9} | Manufacturer:  | Description:  | Designation:  | Label:  | Link_Type: next_report
  Element: Type: embed://import/10_electric/10_allpole/100_folio_referencing/01coming_arrow.elmt | UUID: {0c8bef71-ea93-4f43-b0d2-8d83e717e46c} | Manufacturer:  | Description:  | Designation:  | Label:  | Link_Type: previous_report
  Element: Type: embed://import/10_electric/10_allpole/100_folio_referencing/01coming_arrow.elmt | UUID: {dfebacfd-0148-41f0-afce-14ee9d7fab9e} | Manufacturer:  | Description:  | Designation:  | Label:  | Link_Type: previous_report
---------------
  Leiter: Terminal1: Element: {2de121e3-fb78-48a4-8f9a-bfee50276de9} | Manufacturer:  | Designation:  | Label:  | UUID: {975add6f-4ba5-44af-a4c0-e1f1c2024601} | Name:  | 
          Terminal2: Element: {0c8bef71-ea93-4f43-b0d2-8d83e717e46c} | Manufacturer:  | Designation:  | Label:  | UUID: {d7fd0bec-9f05-4651-a50b-29d7ffabeb41} | Name:  | 
          TensionProtocol:  | Function:  | Text: L1 | Cable:  | Color:  | CrossSection: 
  Leiter: Terminal1: Element: {f253c71e-38a7-4155-8ab4-a844ced1a227} | Manufacturer:  | Designation:  | Label: KA1 | UUID: {b3b3dc63-1c98-409b-ab79-3dbaea3556cb} | Name: 13 | 
          Terminal2: Element: {dfebacfd-0148-41f0-afce-14ee9d7fab9e} | Manufacturer:  | Designation:  | Label:  | UUID: {d7fd0bec-9f05-4651-a50b-29d7ffabeb41} | Name:  | 
          TensionProtocol:  | Function:  | Text:  | Cable:  | Color:  | CrossSection: 
  Leiter: Terminal1: Element: {0a20780e-16b6-4198-b487-a0a22c37b1a0} | Manufacturer:  | Designation:  | Label: KA1 | UUID: {8d0fa333-2d98-4a75-8a4e-21c81cce7ec3} | Name: A1 | 
          Terminal2: Element: {f253c71e-38a7-4155-8ab4-a844ced1a227} | Manufacturer:  | Designation:  | Label: KA1 | UUID: {b9683546-f0a2-4386-b114-ef1d46b2df3d} | Name: 14 | 
          TensionProtocol:  | Function:  | Text: 10 | Cable:  | Color:  | CrossSection: 
---------------
---------------
QET-Projekt     : Title: test_terminal_name | FileName: test_terminal_name (3) | FilePath: /home/ich/Projekte/c_c++/QET_CablePlan/test_terminal_name (3).qet | SaveDate: 19.06.24 | SaveTime: 13:00
Anzahl Diagramme: 2
Anzahl Elemente : 8
Anzahl Leiter   : 6
---------------
  Element: Type: embed://import/10_electric/10_allpole/310_relays_contactors_contacts/01_coils/bobine3.elmt | UUID: {0a20780e-16b6-4198-b487-a0a22c37b1a0} | Manufacturer:  | Description:  | Designation:  | Label: KA1 | Link_Type: master | Linked with: {c31acffc-355c-4720-b8c9-f898854c4f96}
  Element: Type: embed://import/10_electric/10_allpole/100_folio_referencing/02going_arrow.elmt | UUID: {485965c2-5b29-4837-9d80-39f7771b066d} | Manufacturer:  | Description:  | Designation:  | Label:  | Link_Type: next_report | Linked with: {9e50f760-832d-4d89-997b-c069d3768c11}
  Element: Type: embed://import/10_electric/10_allpole/310_relays_contactors_contacts/02_contacts_cross_referencing/01_auxiliary_contacts/con_simple.elmt | UUID: {f253c71e-38a7-4155-8ab4-a844ced1a227} | Manufacturer:  | Description:  | Designation:  | Label: KA2 | Link_Type: slave | Linked with: {ab3f9e64-382d-4f46-b777-7e64df3c842e}
  Element: Type: embed://import/10_electric/10_allpole/100_folio_referencing/01coming_arrow.elmt | UUID: {9e50f760-832d-4d89-997b-c069d3768c11} | Manufacturer:  | Description:  | Designation:  | Label:  | Link_Type: previous_report | Linked with: {485965c2-5b29-4837-9d80-39f7771b066d}
  Element: Type: embed://import/10_electric/10_allpole/310_relays_contactors_contacts/02_contacts_cross_referencing/01_auxiliary_contacts/con_simple.elmt | UUID: {ab572a73-ab0c-4a10-bfc2-7b6d643a02d3} | Manufacturer:  | Description:  | Designation:  | Label: KA3 | Link_Type: slave | Linked with: {f0307d85-136f-44c8-9845-21138432b71e}
  Element: Type: embed://import/10_electric/10_allpole/310_relays_contactors_contacts/01_coils/bobine3.elmt | UUID: {ab3f9e64-382d-4f46-b777-7e64df3c842e} | Manufacturer:  | Description:  | Designation:  | Label: KA2 | Link_Type: master | Linked with: {f253c71e-38a7-4155-8ab4-a844ced1a227}
  Element: Type: embed://import/10_electric/10_allpole/310_relays_contactors_contacts/02_contacts_cross_referencing/01_auxiliary_contacts/con_simple.elmt | UUID: {c31acffc-355c-4720-b8c9-f898854c4f96} | Manufacturer:  | Description:  | Designation:  | Label: KA1 | Link_Type: slave | Linked with: {0a20780e-16b6-4198-b487-a0a22c37b1a0}
  Element: Type: embed://import/10_electric/10_allpole/310_relays_contactors_contacts/01_coils/bobine3.elmt | UUID: {f0307d85-136f-44c8-9845-21138432b71e} | Manufacturer:  | Description:  | Designation:  | Label: KA3 | Link_Type: master | Linked with: {ab572a73-ab0c-4a10-bfc2-7b6d643a02d3}
---------------
  Leiter: Terminal1: Element: {0a20780e-16b6-4198-b487-a0a22c37b1a0} | Manufacturer:  | Designation:  | Label: KA1 | UUID: {8d0fa333-2d98-4a75-8a4e-21c81cce7ec3} | Name: A1 | 
          Terminal2: Element: {f253c71e-38a7-4155-8ab4-a844ced1a227} | Manufacturer:  | Designation:  | Label: KA2 | UUID: {b9683546-f0a2-4386-b114-ef1d46b2df3d} | Name: 14 | 
          TensionProtocol:  | Function:  | Text: 10 | Cable:  | Color:  | CrossSection: 
  Leiter: Terminal1: Element: {f253c71e-38a7-4155-8ab4-a844ced1a227} | Manufacturer:  | Designation:  | Label: KA2 | UUID: {b3b3dc63-1c98-409b-ab79-3dbaea3556cb} | Name: 13 | 
          Terminal2: Element: {485965c2-5b29-4837-9d80-39f7771b066d} | Manufacturer:  | Designation:  | Label:  | UUID: {975add6f-4ba5-44af-a4c0-e1f1c2024601} | Name: 1 | 
          TensionProtocol:  | Function:  | Text: 42 | Cable:  | Color:  | CrossSection: 
  Leiter: Terminal1: Element: {9e50f760-832d-4d89-997b-c069d3768c11} | Manufacturer:  | Designation:  | Label:  | UUID: {d7fd0bec-9f05-4651-a50b-29d7ffabeb41} | Name: 1 | 
          Terminal2: Element: {ab572a73-ab0c-4a10-bfc2-7b6d643a02d3} | Manufacturer:  | Designation:  | Label: KA3 | UUID: {b3b3dc63-1c98-409b-ab79-3dbaea3556cb} | Name: 13 | 
          TensionProtocol:  | Function:  | Text: 42 | Cable:  | Color:  | CrossSection: 
  Leiter: Terminal1: Element: {ab3f9e64-382d-4f46-b777-7e64df3c842e} | Manufacturer:  | Designation:  | Label: KA2 | UUID: {8d0fa333-2d98-4a75-8a4e-21c81cce7ec3} | Name: A1 | 
          Terminal2: Element: {c31acffc-355c-4720-b8c9-f898854c4f96} | Manufacturer:  | Designation:  | Label: KA1 | UUID: {b9683546-f0a2-4386-b114-ef1d46b2df3d} | Name: 14 | 
          TensionProtocol:  | Function:  | Text: 10 | Cable:  | Color:  | CrossSection: 
  Leiter: Terminal1: Element: {f0307d85-136f-44c8-9845-21138432b71e} | Manufacturer:  | Designation:  | Label: KA3 | UUID: {8d0fa333-2d98-4a75-8a4e-21c81cce7ec3} | Name: A1 | 
          Terminal2: Element: {ab572a73-ab0c-4a10-bfc2-7b6d643a02d3} | Manufacturer:  | Designation:  | Label: KA3 | UUID: {b9683546-f0a2-4386-b114-ef1d46b2df3d} | Name: 14 | 
          TensionProtocol:  | Function:  | Text: 13 | Cable:  | Color:  | CrossSection: 
  Leiter: Terminal1: Element: {9e50f760-832d-4d89-997b-c069d3768c11} | Manufacturer:  | Designation:  | Label:  | UUID: {d7fd0bec-9f05-4651-a50b-29d7ffabeb41} | Name: 1 | 
          Terminal2: Element: {c31acffc-355c-4720-b8c9-f898854c4f96} | Manufacturer:  | Designation:  | Label: KA1 | UUID: {b3b3dc63-1c98-409b-ab79-3dbaea3556cb} | Name: 13 | 
          TensionProtocol:  | Function:  | Text: 42 | Cable:  | Color:  | CrossSection: 
---------------

Go to forum: FR : Aide, suggestions, discussions, ...

61 Reply by plc-user

(26 replies, posted in FR : Aide, suggestions, discussions, ...)

Hallo zusammen!

Das Herausfinden der Verbindungen ist nicht ganz so einfach, wie es auf den ersten Blick scheint: Spätestens, wenn die Verbindung zu einem anderen Folio geht, müssen die Verweise der Referenz-Elemente in die Suche eingebunden werden. Dann gibt es noch Master/Slave-Elemente, wobei die Slaves keine Betriebsmittelkennzeichen haben, diese aber für eine sinnvolle Verwendung in einem Kabelplan nötig ist...
Nicht ganz trivial, die Sache mit dem Kabelplan!

via Online-Translator:

Salut à tous !

Trouver les connexions n'est pas aussi simple qu'il n'y paraît au premier abord : au plus tard lorsque la connexion va vers un autre Folio, les renvois des éléments de référence doivent être intégrés dans la recherche. Ensuite, il y a les éléments maître/esclave, les esclaves n'ayant pas de code d'exploitation, mais celui-ci est nécessaire pour une utilisation judicieuse dans un plan de câblage...
Pas si trivial que ça, le plan de câblage !

Go to forum: FR : Aide, suggestions, discussions, ...

62 Reply by plc-user

(26 replies, posted in FR : Aide, suggestions, discussions, ...)

Salut qmcc,

wahrscheinlich nicht die erhoffte Antwort zu Deiner Frage, aber etwas zum Lesen:
https://qelectrotech.org/forum/viewtopi … 694#p19694

Go to forum: FR : Aide, suggestions, discussions, ...

63 Reply by plc-user

(5 replies, posted in Export DXF)

Hello Andy.nx,

I'm just curious:
Why do you need the proprietary format "dxf" if it doesn't seem to matter which software you can open it with?
Then perhaps free formats (SVG) that can be further processed with free software (Inkscape) could also be considered?

Go to forum: Export DXF

64 Reply by plc-user

(5 replies, posted in Export DXF)

Tried with current version QET 0.10dev:
A dxf-file is created what LibreCAD can open and it looks quite o.k.

Go to forum: Export DXF

65 Reply by plc-user

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

Maybe this helps:
In Element-Editor you can set the property "Width" for dynamic_text.
Then the text is automatically wrapped at spaces.

You can also set the Property "Width" afterwards in design-editor.

Go to forum: EN : Help, suggestions, discussions, ...

66 Reply by plc-user

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

CSE wrote:

I downloaded 0.100-dev and finally I made it work without installation (7zip works fine but windows file administrator fails unzipping all the element nested folders).

Maybe the same "problem" from here?
https://qelectrotech.org/forum/viewtopi … 755#p19755

And:
It's always a good idea, NOT to copy the Ready-To-Use - version to c:\programfiles
try to use something like c:\tools\qet or so...

Go to forum: EN : Help, suggestions, discussions, ...

67 Topic by plc-user

(1 replies, posted in Code)

Hello everybody!

In Element-Editor the Edit-Fields (SpinBoxes) for X- and Y-Position of terminals lose focus every time a key on the keyboard is hit. That makes editing the position with keyboard very annoying!

Trying to fix that, I edited the QET-Sources a bit and now I need someone to check, whether there are any side-effects.
For me it seems to work, but my Qt-Knowledge is very restricted, so I don't know if there may be something wrong.
Actually it compiles without warning!

Here's what I changed:

diff --git a/sources/editor/ui/terminaleditor.cpp b/sources/editor/ui/terminaleditor.cpp
index c84ae5ecf..77e0c2112 100644
--- a/sources/editor/ui/terminaleditor.cpp
+++ b/sources/editor/ui/terminaleditor.cpp
@@ -219,9 +219,9 @@ void TerminalEditor::activeConnections(bool active)
 {
     if (active) {
         m_editor_connections << connect(ui->m_x_dsb, QOverload<qreal>::of(&QDoubleSpinBox::valueChanged),
-                                        this, &TerminalEditor::posEdited);
+                                        [this]() { TerminalEditor::posEdited(); ui->m_x_dsb->setFocus();} ) ;
         m_editor_connections << connect(ui->m_y_dsb, QOverload<qreal>::of(&QDoubleSpinBox::valueChanged),
-                                        this, &TerminalEditor::posEdited);
+                                        [this]() { TerminalEditor::posEdited(); ui->m_y_dsb->setFocus(); } ) ;
         m_editor_connections << connect(ui->m_orientation_cb,  QOverload<int>::of(&QComboBox::activated),
                                         this, &TerminalEditor::orientationEdited);
         m_editor_connections << connect(ui->m_name_le, &QLineEdit::editingFinished,

Could someone please use this diff to check, if it's ok?
Maybe you, Laurent?

In case that code works without side-effects I would create a pull-request on GitHub.

Thanks in advance!
  plc-user

Go to forum: Code

68 Reply by plc-user

(4 replies, posted in Import DXF)

Question:
How can we help if we don't know what's going wrong? No Sample-Files, no screenshots ... nothing!
It's not helpful for potential helpers if someone else writes that he/she has the same problem!

So:
What is going wrong and where?

Maybe this post can help:
https://qelectrotech.org/forum/viewtopi … 901#p19901

Go to forum: Import DXF

69 Reply by plc-user

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

Hello samuelps.hr,

as Laurent already said:
First you need to download the whole sourcecode-package from github
https://github.com/qelectrotech/qelectr … rce-mirror
and unpack to a local directory.

With Qt-Linguist you open one or more ts-files from that directoy-structure.
My suggestion: qet_pt, qet_pt_BR and qet_en
Then you can compare the translations.

When you look at the columns on the left and push the mouse-cursor over the symbols, you can see the "completion-status" for that translation. As you can see: There are many question-marks for Portuguese. In the screenshot you see that there is a translation for Portuguese, but the translator wasn't sure, if this translation is correct. When you say it's correct, set the status to "done", otherwise correct the phrase and then mark as done.

When finished you can "release" the language-files and publish them here (qet_pt.ts and qet_pt.qm) as ZIP or create a pull-request at github, if you have an account. But I guess Laurent would be happy to upload the files to github, if you post them here...!

Best regards
  plc-user

Go to forum: EN : Help, suggestions, discussions, ...

70 Reply by plc-user

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

Hello samuelps.hr

Looking at the language-files:
There are many translations missing or still declared "unfinished" (1921) for Portuguese!
There are even more translations for Brazilian Portuguese finished: only 51 declared "unfinished".
Maybe this is a good start for you to help the other Portuguese QET users and complete the Portuguese translations?

EDIT:
scorpio810 wrote a little manual:
https://qelectrotech.org/forum/viewtopi … 375#p13375

Best regards
  plc-user

Go to forum: EN : Help, suggestions, discussions, ...

71 Reply by plc-user

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

Can you give a simple example of your art here so that others can benefit from it?
Thanks in advance!

Go to forum: EN : Help, suggestions, discussions, ...

72 Reply by plc-user

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

By default, the slave elements do not have their own labelling as they are usually an integral part of the master element (relay contact etc.). I therefore assume that this is probably not possible at the moment.
A similar request came up some time ago: switches with knobs, push rods, etc., which must appear somewhere in the parts list, too.

Go to forum: EN : Help, suggestions, discussions, ...

73 Reply by plc-user

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

Please read edited part (second half) from here:
https://qelectrotech.org/forum/viewtopi … 897#p19897

Go to forum: EN : Help, suggestions, discussions, ...

74 Reply by plc-user

(2 replies, posted in DE : Hilfe, Vorschläge, Unterhaltungen...)

Es wäre schön, wenn der Ersteller hier einen Hinweis auf den anderen Thread geben würde, in dem er dieselbe Frage noch einmal gestellt hat und Hinweise für die Abhilfe seines Problems bekommen hat!
Danke!

Go to forum: DE : Hilfe, Vorschläge, Unterhaltungen...

75 Reply by plc-user

(4 replies, posted in Elements)

Does anybody know, if jubert.loic is still alive?
He did not answer, if the suggestion helped, nor did he say "thanks" for the help!

Go to forum: Elements