Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.
Hello,
We are currently using Projeqtor V9.4.3 and plug-in Customization of screens V6.0.We are encountering 2 strange behaviors.
First we have a message, in the plug-in screen for Organisation, displaying that we have to use version 5.0 or superior (see error_message). But we are already using a far superior version of the plug-in…
Second, in the plug-in screen for project. We cannot move some fields (for example « en construction ») to other part of the screen.The field « placer après le champ » (place after the field) cannot be selected. (see edit_file).It seems that it is fields from the Traitement block (see block).
Can you provide help for both of these errors ?
Thanks
Best regards
First we have a message, in the plug-in screen for Organisation, displaying that we have to use version 5.0 or superior (see error_message). But we are already using a far superior version of the plug-in…
This message is not blocking.
In most cases you won't see any effet.
We are working on fix of plugin to improve this side.
Second, in the plug-in screen for project. We cannot move some fields (for example « en construction ») to other part of the screen.The field « placer après le champ » (place after the field) cannot be selected. (see edit_file).It seems that it is fields from the Traitement block (see block).
The fields of "Progress" (for project progress or activity progress) are mostly displayed in table (columns and lines) so cannot be moved.
Ok for the message, we will just ignore it now.
With a previous version of Projeqtor (V9.2.4), we had the possibility to change the field "en construction" (see attached file) from Traitement to Avancement. So we cannot do the same with the latestest version ?
Well in fact "Under construction" should be "changeable"
Maybe it is sid eeffect of another restriction.
We'll have a look and possible improve this on next version of plugin.