Hum...I dont understand why the "Check Object to Copper Area" checkbox is not checked by default...

## This checkbox: 

# NO MODIFICATION DETECT WHEN REBUILD COPPER AREA 1. Create a PCB like that with one track and copper area  2. Save the file 3. Move the track (As you see DRC dont detect copper are colision, you need to check the "Check Object Copper Area" in DCR config  4. Save the file with the colision 5. Rebuild copper area, No modification is detected, no "*" on tab so you think modification are already saved  6. Dont save, close the tab (No warning on not saved PCB) 7. Reopen the PCB, the error is still here

Hi That's because of your PCB haven't rebuld the copper area before share, then you will see the track overlap the copper. and your partner can't see this, because the PCB will rebuild the copper area if it is opening at first time. the new PCB doesn't enable the "Check Object to Copper Area ", that needs enable manually. and for step4 and step5, I can't repeat it, the (*) mark is working. can you repeat it again?

Hello @UserSupport, Many thanks for your return. > "...That's because of your PCB haven't rebuld the copper area before share,..." I can guarantee project is transferred to team just after the empty project is created... and even though why it's not synced with error or not ? > "...the new PCB doesn't enable the "Check Object to Copper Area..." Ok now I see, but from my point of view, I see ground plane like a kind of "track" and I think by default the DCR must do "All check" or "Nothing"... Actually default DCR config behave like "half checker"... I wonder in wich case someone who didn't want to check copper area short circuit ? > "...and for step4 and step5, I can't repeat it, the (*) mark is working...." Ok I will retry and let you known

Ok @UserSupport, I can confirm the (*) bug, try under [https://easyeda.com/rom1nux/shared](https://easyeda.com/rom1nux/shared) (PCB : UserSupport_CopperArea), you are developer on this project 1. Open the PCB, the CopperArea will be recreated (I don't understand why it's not truly synced "in the state" but it's another debate) 2. Move the track and save the file, close it and reopen it, you will get something like that  3. Just rebuild the copper area  You can see copper area is well reconstructed but change in file is not detected, (no "*") you can close file without warning, etc... Thanks for your support

Hi I still can not repeat the (no *) issue. can you try close the browser and remove the cache and try again? for the copper area issue "(I don't understand why it's not truly synced "in the state" but it's another debate)" that is because of the copper area fill data is saved at the local store, which is name as IndexedDB,  [https://w3c.github.io/IndexedDB/](https://w3c.github.io/IndexedDB/) the PCB file only save the copper area outline data, when your team member open the PCB at the first time, the editor will rebuild the copper area automatically, and save the copper area fill data to IndexedDB(browser local storage), and when open this PCB again, the copper area fill data will be reading from IndexedDB. That means your copper area fill data doesn't macth your member's copper area fill data if you don't rebuild it and save, even they are the same one PCB file. Why IndexedDB?  at v5.9, for resolve the big file can not be saved at the server, we change the PCB fill data to local IndexedDB. A PCB's copper area fill data is very large, that cause a lot storage, and if the file is too big it will not allow to save to the server. example: v5.7 with copper fill data: need to save 11MB to server  v5.9 no fill data, using IndexedDB: the same file, only need to save 1.5MB to the server.  and the other way, when the fill data reading from local that will fast than from the server. Sorry for the confuse,  I hope you can understand. thank you :)