Hi,
In Flowcode10, the Find/Replace command in the View Menu currently does not return any search results
when searching for a Port bit used by an INPUT or OUTPUT component.
Sasi
Problem with the Find/Replace command.
-
- Posts: 91
- http://meble-kuchenne.info.pl
- Joined: Wed Dec 02, 2020 12:11 pm
- Has thanked: 36 times
- Been thanked: 9 times
-
- Matrix Staff
- Posts: 1465
- Joined: Sat Dec 05, 2020 10:32 am
- Has thanked: 204 times
- Been thanked: 347 times
Re: Problem with the Find/Replace command.
Thank you very much for the bug report. It will be addressed in a future release of Flowcode.
-
- Matrix Staff
- Posts: 1465
- Joined: Sat Dec 05, 2020 10:32 am
- Has thanked: 204 times
- Been thanked: 347 times
Re: Problem with the Find/Replace command.
It looks like port and pin values in the i/o commands were never checked during a search, so I think this is a long-standing problem.
We have no current plans for an update patch for the v10 release.
We have no current plans for an update patch for the v10 release.
Re: Problem with the Find/Replace command.
Hi Steve,
Thanks for the replies.
I used this feature regularly and still use it in Flowcode8 and 9.
In my Flowcode10 project from a year ago, there are also signs that I was using the Find/Replace feature to search for portbits.
It's possible that it broken after installing the v10.1.2 patch.
This bug is not a big problem, it's just less comfortable to use it that way.
Regards,
Sasi
Thanks for the replies.
I used this feature regularly and still use it in Flowcode8 and 9.
In my Flowcode10 project from a year ago, there are also signs that I was using the Find/Replace feature to search for portbits.
It's possible that it broken after installing the v10.1.2 patch.
This bug is not a big problem, it's just less comfortable to use it that way.
Regards,
Sasi
-
- Matrix Staff
- Posts: 1465
- Joined: Sat Dec 05, 2020 10:32 am
- Has thanked: 204 times
- Been thanked: 347 times
Re: Problem with the Find/Replace command.
I just checked and the initial release of v10 also has this problem. Although it was working on in v9.
I have found and fixed the issue, so a future release of Flowcode should not have this problem.
I have found and fixed the issue, so a future release of Flowcode should not have this problem.