In addition to FCV5 Pro, I currently have FCV6 PIC package edition for personal evaluation so comments based on that.
A few personal thoughts and suggestions...
1. I find the pop-up box, declaring total run time after stopping code execution, merely irritating and never useful. The ability to disable it would be welcome.
2. I only ever use the dashboard panel with the basic 2D components, though associated icon labels would be good (i.e. without having to individually attach and group text labels).
3. As a basic productivity feature, the ability to group-select flow icons and create a new macro from selected would be good (e.g. Select > Right-click > Create New Macro). Possibly coupled with an option to simultaneously convert the selected icons in the flow to the newly-created macro at the same time (e.g. Select > Right-click > Convert to macro), aiding quick hierarchical decomposition and structure as the code develops and grows.
4. Option to remove component icons from the drop-downs (i.e. Different graphical styles unnecessary when only debug indication is needed).
5. If the system panel is deselected, it doesn't automatically load and open if the component is mistakenly directed to the wrong panel when selected (obviously visa-versa to suit others preferring the system panel). Ideally the panel options would be parentally limited by the 'View' options menu.
6. An ability to custom-colour macro tabs.
7. ...Oh, and I2C slave would be welcome
As a newcomer to FCV6 my apologies if I've overlooked/missed anything.
Keep up the fine work gentlemen, and thanks for your consideration
All the best,
Brendan
A few thoughts...
Moderator: Benj
Forum rules
Only feature requests will be considered here. General questions should not be posted in this forum.
Only feature requests will be considered here. General questions should not be posted in this forum.
- JonnyW
- Posts: 1230
- Joined: Fri Oct 29, 2010 9:13 am
- Location: Matrix Multimedia Ltd
- Has thanked: 63 times
- Been thanked: 290 times
- Contact:
Re: A few thoughts...
Afternoon Brendan.
I hope this answers some of these points.
Jonny
This has been asked for a few times. It is something I keep meaning to do, and is not a big job at all so I will try to get that sorted.1. I find the pop-up box, declaring total run time after stopping code execution, merely irritating and never useful. The ability to disable it would be welcome.
Connections on components have been asked for, I think we just need to look at the cleanest way of doing this. There is an option in the latest patch to entirely disable the system panel.2. I only ever use the dashboard panel with the basic 2D components, though associated icon labels would be good (i.e. without having to individually attach and group text labels).
Unfortunately this isn't so straight-forward when local variables or parameters are used - how are these to be converted in the sub-macro. It is not impossible, but I would have to have a bit of free time to add this nicely.3. As a basic productivity feature, the ability to group-select flow icons and create a new macro from selected would be good (e.g. Select > Right-click > Create New Macro). Possibly coupled with an option to simultaneously convert the selected icons in the flow to the newly-created macro at the same time (e.g. Select > Right-click > Convert to macro), aiding quick hierarchical decomposition and structure as the code develops and grows.
Things are getting very cluttered. It would be nice for the user to be able to hide components, but then how would they get them back. The other option is to add 'uncategorised' into the component on export. Perhaps a combination of these two, but we definitely need to do something in this area pretty quickly I think.4. Option to remove component icons from the drop-downs (i.e. Different graphical styles unnecessary when only debug indication is needed).
This is fixed in the next patch.5. If the system panel is deselected, it doesn't automatically load and open if the component is mistakenly directed to the wrong panel when selected (obviously visa-versa to suit others preferring the system panel). Ideally the panel options would be parentally limited by the 'View' options menu.
Interesting. I would like to be able to group them into folders in the project explorer. Variables too. These sorts of things would be good to add when there is a bit of quiet time.6. An ability to custom-colour macro tabs.
Do we not have one? Shows how much I know. This is one for any component creators I think.7. ...Oh, and I2C slave would be welcome
I hope this answers some of these points.
Jonny
-
- Posts: 243
- Joined: Tue Nov 27, 2012 12:53 pm
- Location: Cambridge, UK
- Has thanked: 140 times
- Been thanked: 118 times
- Contact:
Re: A few thoughts...
Thank you Jonny.
I'll admit to feeling rather guilty throwing in a wish-list as I'm sure you've more than enough on your plate.
The progressive evolution of Flowcode does make such a compelling case
All the best,
Brendan
I'll admit to feeling rather guilty throwing in a wish-list as I'm sure you've more than enough on your plate.
The progressive evolution of Flowcode does make such a compelling case
All the best,
Brendan
LinkedIn Profile...
http://www.linkedin.com/in/brendantownsend
http://www.linkedin.com/in/brendantownsend
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: A few thoughts...
3. As a basic productivity feature, the ability to group-select flow icons and create a new macro from selected would be good (e.g. Select > Right-click > Create New Macro). Possibly coupled with an option to simultaneously convert the selected icons in the flow to the newly-created macro at the same time (e.g. Select > Right-click > Convert to macro), aiding quick hierarchical decomposition and structure as the code develops and grows.
Labview does this very well and I agree it is a nice feature. I wonder if global variables should stay as globals or if they should be recreated as locals and passed in as parameters from the component. Maybe some kind of a pop up wizard which analyses the variables and gives you options for each.Unfortunately this isn't so straight-forward when local variables or parameters are used - how are these to be converted in the sub-macro. It is not impossible, but I would have to have a bit of free time to add this nicely.
I2C slave is now officially on my list, hopefully an easy one to sign off and roll out, mainly an FCD upgrade required I would think to add necessary interrupts. Not sure how a software one would work but should be possible. SPI slave would be another good one.7. ...Oh, and I2C slave would be welcome
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
-
- Posts: 243
- Joined: Tue Nov 27, 2012 12:53 pm
- Location: Cambridge, UK
- Has thanked: 140 times
- Been thanked: 118 times
- Contact:
Re: A few thoughts...
Hi Ben.
Thanks for your thoughts and comments.
I can't speak for everyone of-course so I'll step aside for other comments.
Excellent news regarding I2C / SPI slave (thank you).
All the best,
Brendan
Thanks for your thoughts and comments.
Recognising things aren't always so simple, I'd 'personally' be happy if they simply retained global status.I wonder if global variables should stay as globals or if they should be recreated as locals and passed in as parameters from the component
I can't speak for everyone of-course so I'll step aside for other comments.
Excellent news regarding I2C / SPI slave (thank you).
All the best,
Brendan
LinkedIn Profile...
http://www.linkedin.com/in/brendantownsend
http://www.linkedin.com/in/brendantownsend