Minor suggestion for B4A 2.70 BETA 1

[NJDude]

The following sub:

Sub DesignerCreateView

Shouldn't it be set as PRIVATE? changing from Public to Private triggers a warning (Sub DesignerCreateView is not used - warning #12)

 

[Erel]

It is actually better to keep it public. Otherwise if you compile your class into a library this method will not be exposed and then the designer will not be able to find it.

 

[Laurent95]

Hello,

Another thing that would be nice also about beta 2.7
Can we clear the previous warning messages wen we have fix them ?
( For be honest this beta is really welcome, i had a lot of warnings in my project, hahahaha. )
Thanks for reply Erel, if it's possible.

Congrats for this release, for now i have only tested the warnings, that's good work.

 

[Erel]

Can we clear the previous warning messages wen we have fix them ?

The warnings are checked whenever you save the project (or press Alt + 2).

 

[Laurent95]

The warnings are checked whenever you save the project (or press Alt + 2).

Hi Erel,

Indeed, thank you.
:signOops: not seen "Alt 2" in the thread

Another question please.

You can also disable warning from a specific type in the module by adding the #IgnoreWarning attribute.
For example to disable warnings #10 and #12:

#IgnoreWarnings: 10, 12

Where i must put it ? I have many modules and activities in my project.
I put this in "Main" module

#Region Project Attributes
   #IgnoreWarnings: 14   
#End Region

#Region Module Attributes
   #FullScreen: False
   #IncludeTitle: False
   #ApplicationLabel: Money Converter
   #VersionCode: 1
   #VersionName: 1.3.0
   #SupportedOrientations: unspecified
   #CanInstallToExternalStorage: False
#End Region

But i still have always the warning about files not used, that i use by code.
(warning 14), that rots the warning's engine window, lolllllllll.
Thanks for the reply.
Regards.

 

[Erel]

It should be in the main module. It is a bug that this warning is not disabled. Will be fixed for the final version.

 

[NJDude]

It is actually better to keep it public. Otherwise if you compile your class into a library this method will not be exposed and then the designer will not be able to find it.

But that will also show in the intellisense and will confuse the user, correct?

 

[Erel]

If you set it to public then it will show.

 

[Laurent95]

It should be in the main module. It is a bug that this warning is not disabled. Will be fixed for the final version.

Thank you Erel.