P Pendrush Well-Known Member Licensed User Longtime User Jun 12, 2015 #1 I use this CustomBuildAction B4X: #CustomBuildAction: 1, c:\windows\system32\attrib.exe, +r res\*.* /s #CustomBuildAction: 4, c:\windows\system32\attrib.exe, -r res\*.* /s but after debugging my app (in rare cases) B4A delete all folders from res directory except drawable, layout and xml. So my folders drawable-xxxhdpi, drawable-xxhdpi, drawable-xhdpi, etc, are deleted.
I use this CustomBuildAction B4X: #CustomBuildAction: 1, c:\windows\system32\attrib.exe, +r res\*.* /s #CustomBuildAction: 4, c:\windows\system32\attrib.exe, -r res\*.* /s but after debugging my app (in rare cases) B4A delete all folders from res directory except drawable, layout and xml. So my folders drawable-xxxhdpi, drawable-xxhdpi, drawable-xhdpi, etc, are deleted.
DonManfred Expert Licensed User Longtime User Jun 12, 2015 #2 the files in this folder (everything under res\) should be writeprotected. Or use a custom Resourcefolder set with #additionalres
the files in this folder (everything under res\) should be writeprotected. Or use a custom Resourcefolder set with #additionalres
P Pendrush Well-Known Member Licensed User Longtime User Jun 12, 2015 #3 Yes i know, but syntax I have posted, worked fine until B4A v5.xx.
Erel B4X founder Staff member Licensed User Longtime User Jun 12, 2015 #4 Did you see whether the the custom actions were executed (in the compilation window)? I agree with @DonManfred that it is better to use #AdditionalRes for this.
Did you see whether the the custom actions were executed (in the compilation window)? I agree with @DonManfred that it is better to use #AdditionalRes for this.
P Pendrush Well-Known Member Licensed User Longtime User Jun 12, 2015 #5 Erel said: Did you see whether the the custom actions were executed (in the compilation window)? Click to expand... I really did not pay attention.
Erel said: Did you see whether the the custom actions were executed (in the compilation window)? Click to expand... I really did not pay attention.