[Solved] Reference to bsSolid gives identifier not found

[Wilko500]

Laz 4.1 FPC 3.2.2 running on macOS Sequoia
My test Chart program works, all defined in Form1/unit1.  I wanted to gather together all the code used by my Chart procedures into a separate unit, U_EnergyHarvest.  This line resulted in bsSolid identifier not found

Code: Pascal  [Select][+][-]

1. Form1.Chart1AreaSeries1.AreaBrush.Style:=bsSolid;  

I was able to fix this by adding FPCanvas (took a while to find this ) to my new units implementation but this was not included in unit1 where the chart was originally defined.

Code: Pascal  [Select][+][-]

1. implementation
2. uses
3.   Unit1, TAGraph, TASeries, TAIntervalSources, TAStyles, FPCanvas, u_aurora, DateUtils;

This is the original uses from unit1

Code: Pascal  [Select][+][-]

1. uses
2.   Classes, SysUtils, Forms, Controls, Graphics, Dialogs, StdCtrls, ExtCtrls,
3.   RichMemo, TAGraph, TASeries, TAIntervalSources, TAStyles, MyUtils, DateUtils,
4.   u_aurora, U_EnergyHarvest;

Please might someone explain why an explicit FPCanvas was needed when code was running from a second unit. 

Ok. I think I solved it. I just discovered that adding Graphics instead of FPCanvas works as well and Graphics was in the original uses, but I don't recall why I added it.  Maybe a requirement of TChart??

[wp]

Graphics is one of the most elemental LCL units, it is added to the uses clause for every form unit by default ("form unit" = unit linked to an lfm form). But when you add a new stand-alone unit to the project there are only Classes and SysUtils in the uses clause.

[Wilko500]

Thank you for confirming that. When I think of the number of new applications I have created and I never noticed that Graphics was always there.

PS: I have been reading number of your posts on labelling chart axis and have found them very helpful, thank you.   I will soon have a much more challenging question on that very subject.