Flowcode Support Board

Posted: **Fri Jan 27, 2023 1:37 pm**

We have become aware of a number of small issues with the initial release. Many have already been fixed and a patch will be released sometime in the next few weeks. Here are some details with suitable workarounds if applicable:

Free targets incorrectly listed as unlicensed (using red "!") in the "Choose a target" list. Also, some targets under "misc" categories are unlicensed and should have the "!" symbol.
- This is a cosmetic bug and they can be chosen normally [FIXED]
Dragging icons onto a State Diagram macro may cause Flowcode to crash [FIXED]
- To avoid this, right-click in the State Diagram window to add icons instead of dragging from Project Explorer or the Ribbon
- Note, this is a pro feature
App Developer projects do lot allow creation of State Diagram macros [FIXED]
- Note, this is a pro feature
App Developer projects cannot show macros using alternative views (State Diagrams, Blocks and Pseudocode) [FIXED]
- Note, this is a pro feature
Source code for components was missing from the wiki [FIXED]
- This was a website error and has been corrected without requiring a patch
Setting properties for a component on a 2d panel too quickly (e.g. in a While loop with a delay less than 1ms) can cause Flowcode's UI to lock when simulation is running [FIXED]
- This could include writing property values directly or when values are written by component macro calls
- The workaround for this is to include a small 1ms Delay icon within any loops. This will not be necessary once an update is released.
- The attached "property write bug" project explains the issue
Double-clicking a component on the toolbar adds it to the wrong panel [FIXED]
- As a workaround, drag the component to a panel or right-click and select "Add to panel..."
The 3D LED component does not update to show its status [FIXED]
- A fix for this is now available via library updates

Posted: **Mon Jan 30, 2023 3:35 pm**

I have just added a couple of known bugs to the above list.

Posted: **Wed Feb 01, 2023 11:45 am**

Found a small bug in constant handling.

Create a local string constant t[20] initial value ""

Then when I'd looked up the initial value - I went to change the constant by double clicking on it in the constant list - FC locks and then closes..

Works okay for a variable.

Martin

Posted: **Wed Feb 01, 2023 11:54 am**

mnfisher wrote: ↑
Wed Feb 01, 2023 11:45 am
Found a small bug in constant handling.

Thanks - I've replicated it and will work on a fix.

Posted: **Wed Feb 01, 2023 6:31 pm**

Not sure if this is a bug or my misunderstanding?

On the esp32 - trying to use a WebServer component. I have wlan_esp32 and NetworkComms component added. There is a 'link to' field in properties - in v9 this would link to the network comms component. In v10 I can't select anything (so incorrect component added?) and there is no tooltip to suggest what I should be looking for?

: webserver.png (94.59 KiB) Viewed 4633 times

v9 is left and v10 on the right - field in 'properties'. Any pointers here?

Martin

Posted: **Thu Feb 02, 2023 9:18 am**

Martin - I believe that is one of @BenR's components and so I'll let him answer that one.

Posted: **Sat Feb 11, 2023 6:05 pm**

Another slight oddity (which I think is new) - if I set a new property as a digital output pin (and this probably affects ports etc as well) - say 'output'.

In a calculation - output = 1 - this gives an error if output is 'unconnected'. This may be intentional- but has caught me a couple of times when I've added an output pin without deciding which pin it is to be at the time. I'd expect the error to occur at compilation?

Martin

Posted: **Sat Feb 11, 2023 9:30 pm**

I hit an issue trying to use the esp_rmt component.

Adding the component to FC - Initialise and SetBuffer(... gives

R:\rmt.h:92:61: error: 'MX_RMT_BUFFER_1' undeclared (first use in this function); did you mean 'MX_RMT_BUFFER_X'?

Looking at the ESP_CAL_RMT.c and the component source file - it looks like the line

Code: Select all

#define MX_RMT_BUFFER_X			CAL_APPEND(MX_RMT_BUFFER_, MX_RMT_NUM)

should create a this buffer (MX_RMT_BUFFER_1), or maybe #defined in EV_AddHeader?

I can't see how to get this to 'create'??

Martin

Posted: **Mon Feb 13, 2023 10:01 am**

Thanks Martin,

The IO property bug is something that was causing problems and I beleive this has now been fixed in the coming update.

For the ESP RMT problem I got a slightly different error to you to do with the TX function not matching the definition.

Hopefully resolved for you now, we had already fixed it but for some reason it hadn't been pushed out on the update system. I've now checked the rest of the CAL files and this appears to be the only one that slipped the net.

Could just have been my local CAL files but anyway the latest is now on the update system.

The error you're getting could be because the component macros are not being called and so most of the code isn't being generated but some still is. If you still have the problem can you attach the project so I can investigate what might be going wrong.

Posted: **Mon Feb 13, 2023 2:15 pm**

Thanks Ben,

I'll try again this evening - I'd worked around it by defining a buffer in supplementary code.

Martin

Flowcode Support Board

Bugs in initial v10 release

Bugs in initial v10 release

Re: Bugs in initial v10 release

Re: Bugs in initial v10 release

Re: Bugs in initial v10 release

Re: Bugs in initial v10 release

Re: Bugs in initial v10 release

Re: Bugs in initial v10 release

Re: Bugs in initial v10 release

Re: Bugs in initial v10 release

Re: Bugs in initial v10 release