When I select the element, I can move it down, but when I press up arrow it does not react.
Thanks for reporting this bug. I committed a fix for it today. If you experience any other strange behavior please report it.
You are not logged in. Please login or register.
QElectroTech → Posts by dfochi
Pages 1
When I select the element, I can move it down, but when I press up arrow it does not react.
Thanks for reporting this bug. I committed a fix for it today. If you experience any other strange behavior please report it.
Basic video showing some capabilities of Conductor and Element Variables and the Update Policy:
https://download.qelectrotech.org/qet/f … olicy.webm
Revision: 4680
Author: dfochi
Date: 2016-09-01 21:41:49 +0200 (Thu, 01 Sep 2016)
Log Message:
-----------
Update Policy now works with conductor autonumberings
With this commit user can now set wheter to freeze or unfreeze conductor labels. I will make a video about this and post it as soon as I can
Revision: 4674
Author: dfochi
Date: 2016-08-29 17:37:42 +0200 (Mon, 29 Aug 2016)
Log Message:
-----------
Conductor Autonum now works with variables. Folio Autonumberings added to conductor autonum
This is the final transition of conductor autonumbering to variables. So now conductor autonumberings work with Folio Numberings (this is the biggest change). There is a lot of class renaming and deletion so the methods can work with both conductor and element autonums. Also, I expect to commit the Update Policy for Conductors as well so that user can set when the variables will be updated or not. Since there is a lot of lines added I expect some bugs to be found but I tried to make the code compatible with element autonum (there is still room for improvement in the compatibility) so that it would be easier to correct bugs.
Basic shapes are definitely facing some bugs with arrow keys. This last commit that I uploaded solved the problem for textfield but not for the other shapes. I will work on a fix for it.
1.
While I'm edting an editable text field of an element placed in the diagram editor, if I use the key "Home" or "End", QET does not move the cursor to the beginning or to the end of the text field but show the first or the last folio of the project. Is it possible to make an exception to use the keys "Home" and "End" in a text field?
2.
If I select an element in the diagram editor and then use the directional keys, they move the element. Right. But if I select several elements, QET move the view of the diagram and not the elements anymore. Is it possible that the directional keys only move the view while no elements are selected?
Revision: 4613
Author: dfochi
Date: 2016-08-08 13:42:47 -0300 (Seg, 08 Ago 2016)
Log Message:
-----------
Fix Home and End Buttons Handling and DiagramEditor Scroll
Hi Nuri, I fixed issue 1. Issue 2 I couldn't replicate it as you described it but I found a bug related to text items. See if it corrected your issue as well.
Problème:
lorsqu'on créé des bobines avec une règle, quand on lie un contact le nom du contact ne prend pas correctement le label de la bobine
Thanks for reporting this galexis. Bug is now corrected
Revision: 4599
Author: dfochi
Date: 2016-07-31 03:30:42 +0200 (Sun, 31 Jul 2016)
Log Message:
-----------
Copy/Paste now works with Element Label Variables
Great work by Joshua, correcting the copy and paste. I added a correction to a minor bug of copying and pasting an element with autonumbering. However there is still some work to do: when we copy and paste an element which does not have it's label frozen we should increment the folio sequential according to its folio. Right now it is only copying the sequential.
Also, when we change the way conductor deals with autonumbering to variables we can also do the same corrections and then the copy and paste will be perfect.
Revision: 4592
Author: dfochi
Date: 2016-07-26 20:52:49 +0200 (Tue, 26 Jul 2016)
Log Message:
-----------
Creation of folio sequential type for Element Autonumbering. Correction of autonumbering type handling in numparteditorw.cpp
I uploaded today a new feature regarding AutoNumbering. Right now it only works with Element AutoNumbering and I plan to extend it to Conductor as well. Now there are 3 new Sequential types:
- Number Format 1 - Folio
- Number Format 01 - Folio
- Number Format 001 - Folio
These sequential types are locked in each Folio. This means that when user adds elements in different folios the sequential will always begin from the initial value user inserted when creating the autonumbering. Also, if user changes between folios the sequential will go back to the last sequential added. Enjoy!
Revision: 4591
Author: dfochi
Date: 2016-07-25 21:18:26 +0200 (Mon, 25 Jul 2016)
Log Message:
-----------
Fix Element Label when opening older QET versions. Fix old user created element label's handling on newer QET versions
Hi friskolon,
I made a commit today that fix the bug of losing element's label information when opening legacy QET projects. Your project should open as expected now. If you experience any other bugs please report them. Thanks for the report.
Revision: 4585
Author: dfochi
Date: 2016-07-20 17:07:21 +0200 (Wed, 20 Jul 2016)
Log Message:
-----------
Added AutoNumbering Management Tab. Update Policy support to Element.
Hey everyone,
I will try to help scorpio on this one:
With this commit you can now set whether you want Element Labels (created with or without autonumbering) to be updated or not. We currently have support only for Element AutoNumbering since the Update Policy makes more sense when dealing with element position in the label (element column and element line). The 4 Update Policies available are:
-Update Only New Elements: only new created Elements will be updated. Existent Element labels will be "frozen". This is useful if you need to move existent elements and do not want their labels to be updated anymore but wishes to update new to be created elements.
-Update Only Existent Elements: only existent Elements will be updated. New Elements will be assigned their formula but will not update once created. I currently do not see a way which this can be useful but since it was trivial to add this option, here it is.
-Both: both new and existent Element labels will be updated. This is the default option and is the way QElectrotech handled element label until now. It is good if you are working on an entirely new project.
-Disable: both new and existent Element labels will not be updated. This is valid for new folios as well. This is a way to stop updates completely. This is useful if you do not want any labels to be updated at all.
Note: The Update Policy DO NOT allow or block autonumberings. It only deals with elements update policy i.e. if their labels are going to be updated or not. If you wish to not use auto numbering you can select the blank selection in autonumbering dock.
Also, you can check if a label is being updated or not by accessing its information and checking if the label has formulas or not.
Pages 1
QElectroTech → Posts by dfochi
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.011 seconds (60% PHP - 40% DB) with 5 queries