Settings and activity
5 results found
-
2 votes
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment 
AdminLari Haapaniemi
(Admin, NAPA)
commented
Hi Marc!
Thank you for the feedback!
This is a good improvement suggestion, and we will add it as an development item. It however might be that the pop-up will be removed in the future versions, since it offers the same functionality as the node library pane. Your suggestion however can be applied to other controls of NAPA Engineer as well.
- Lari
-
2 votes
An error occurred while saving the comment AdminLari Haapaniemi
(Admin, NAPA)
commented
Hi Juho!
Thank you bringing this to our attention!
This is a fair request, and we definitely will look into this! However, the graphics viewer is an area that has its limitations regarding Napa Engineer. Therefore, we cannot promise that all the features that exist for it in Classic Napa will be supported in the Napa Engineer. If a feature cannot be implemented, we will aim to create alternative way to achieve the same result.
-
1 vote
An error occurred while saving the comment AdminLari Haapaniemi
(Admin, NAPA)
commented
Thanks for using the UserVoice!
In Napa Engineer we decided to remove Visual Studio Code to fix the issues we had with backward compatibility and the need for constantly updating it to the latest version. We created a new tool called Text Editor which aims to be even more efficient than the Visual Studio Code, but will be inside Napa Engineer.
It is in the development stage and we will notify the users when it is done. -
1 vote
An error occurred while saving the comment AdminLari Haapaniemi
(Admin, NAPA)
commented
Hi Yashwant Kamath!
Currently in the alpha stage you can report the bugs you encounter with Napa Engineer in the UserVoice channel.
For each issue you report in this channel, we will create a corresponding development task, which we will treat as a priority!
Thank you for your suggestion Radovan!
That is a very good idea, and it also addressed an issue we are aware of.
The neng.getinput in its current form will not be the final solution, and we are still considering whether:
a) We make this statement appear automatically when you have a port.
b) Make the node port ID:s be variables automatically as you suggested.
C) Make it so that when you pass a node as a parameter, you could derive the ports directly from it (e.g. node.PORTROOM).
One thing we want to ensure is that you know that the variable you have is coming from the node port, but the exact way this is defined is still something we are iterating on :)
- Lari