V8 install issue on MAC

[peterhalloway]

Hi All

I am hoping someone may have had a similar problem and has a fix! (always hopeful!)

I am trying to run V8 on Windows 7 Professional, on my MAC via parallels (latest version). When I click new project it goes back to the start page (actually duplicates the start page) but freezes. I have attached a screen shot.

Flowcode 6 works in the same environment.

Does anyone have any ideas on what could be causing this?

Pete

[Steve]

Hi Pete,

I don't have access to a MAC and so can't do much to help, but I will try. I assume you get past the "Choose a target..." screen and Flowcode freezes after you have chosen a chip.

Does this problem happen when you choose other targets too or just some specific ones? And does the problem occur for both embedded and scada projects?

Also, do you get the same issue when trying to open an existing Flowcode project or opening a template file?

Regards,
Steve.

[peterhalloway]

Hi Steve thanks for coming back to me.
It didn't let me do anything with SCADA as I don't have the licences. If I open a template it works, if I try a different target with new project it has the same issue. I am currently trying to work with Raspberry Pi.

Just tried this:

open template, chose arduino. Then I deleted the component macro and the combo board on the panel. Then went into options and changed the target to raspberry Pi. This seemed to work as a workaround. Tomorrow I will check iy programs a target and let you know. If I don't delete the macro and combo board it seems to get caught in a loop.

Many thanks

Pete

[Steve]

Hi Pete,

A template file in Flowcode v8 is essentially just an existing project that is loaded, so It sounds like loading files is not a problem. I've attached a blank Raspberry Pi (3B+) project that might get you around this issue on the MAC. If you save this somewhere and change it so it is read-only so you don't accidentally overwrite it, then you can open this file in Flowcode instead of creating a new project.

I know it's not a fix, but it should be a good enough workaround for you to get it working under the MAC parallels.

Regards,
Steve.

[peterhalloway]

Thanks Steve