You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there are only 2 options if fort detects a new program that creates a connection.
But for example if there is a setup that creates a connection at installation time, I would want to [ ignore ] it and not pollute the programs list with it.
Currently if I click "cancel" it will create an entry and block it (that behavier is OK, just add an ignore option, maybe with a time, to not add an entry and ask again at next connection or after the time expired).
So if I run the setup again it should ask again because it will detect it again as new program.
The text was updated successfully, but these errors were encountered:
OK, yes your right, that works, it is only one click more.
It is a valid question if adding another button is too much on the interface or not.
With an ignore button I would leave the popup open until setup is done and then click ignore to close it.
But yes I think it is just a thing to get used to it to simply enable the timer and then click OK. 👍
And I tested, if I enable the timer and click cancel it will not save the timer.
It could be detected that the user changed a setting and ask if one really want to cancel, but I think it is not needed.
It is a valid question if adding another button is too much on the interface or not.
There will be new buttons after implementing "Ask to connect" mode, to view paused connections list.
I was thinking about adding some "Apply to this Process only and do not create Program entry" action in the popup with "Ask to connect". But the timer is OK)
Currently there are only 2 options if fort detects a new program that creates a connection.
But for example if there is a setup that creates a connection at installation time, I would want to [ ignore ] it and not pollute the programs list with it.
Currently if I click "cancel" it will create an entry and block it (that behavier is OK, just add an ignore option, maybe with a time, to not add an entry and ask again at next connection or after the time expired).
So if I run the setup again it should ask again because it will detect it again as new program.
The text was updated successfully, but these errors were encountered: