set/getProperty deprecate on sdk 4?

I know about 2 copy of properties (had memory problem) so for bigger data set first null and than correct values (system probably set new value and if it is saved correct delete old and change name).

Of course system call onSettingsChanged() but if getProperty is deprecated how to read this settings?

2 copies of settings.. How to manage memory if I don't know how it handle system? How many free memory I have to have?

92kb

- background uknown

- ??? settings 1x or 2x

--??? properties 1x or 2x

We spend hours to fight with limitation of system, the worst it's keeping in my memory code, each lines of code lower my memory, most of variable has 1 or 2 chars, code is horrible. There is graphics pool (bwt what is the size of it), the same should be with code and non user data.

I know about 2 copy of properties (had memory problem) so for bigger data set first null and than correct values (system probably set new value and if it is saved correct delete old and change name).

Of course system call onSettingsChanged() but if getProperty is deprecated how to read this settings?

2 copies of settings.. How to manage memory if I don't know how it handle system? How many free memory I have to have?

92kb

- background uknown

- ??? settings 1x or 2x

--??? properties 1x or 2x

We spend hours to fight with limitation of system, the worst it's keeping in my memory code, each lines of code lower my memory, most of variable has 1 or 2 chars, code is horrible. There is graphics pool (bwt what is the size of it), the same should be with code and non user data.

ok, my minimal is 2.3 and when I've changed to 2.4 none of device was removed (maybe some part numbers, I don't know).

As I understand module Properties should be use to obtain application's settings (even save new data - but not by background) and Storage to save data for later usage and exchange data between background and app, correct?

checking sdk level by e.g.

if(Application has Storage)

{

 //access app's settings by Properties

 //access to storage by Storage

}else

{

 //access app's settings by getProperties()

 //access to storage by set/getProperties()

}

"But what about with the subject of this topic, set/getProperty deprecation? On venu 2/2s sim everything run well it means not deprecated."

Yeah, idk. The doc says not to use that API for CIQ 4 devices so maybe it won't work in the future.

You could always switch to Application.Properties (getValue and setValue).

I know it's a pain bc devices older than 2.4 don't support it. That's why I never use it, but I guess I'll have to if I ever want to support Venu 2.

I don't think that SDK 4 itself can deprecate Applicatoin.AppBase.get/setProperty, bc as Brandon pointed out, it's supposed to work. Otherwise we won't be able to dev for old devices in SDK 4.

I know about properties name. But I think also name of id in in string (<string id="AppName">) and layout (<param name="locX">).

But what about with the subject of this topic, set/getProperty deprecation? On venu 2/2s sim everything run well it means not deprecated.

And due to the way properties are defined and accessed, the original name has to be preserved. (They're stored in a dictionary where the property name is the key.)

"oh no... I've asked about several time and I was almost sure that length of var name has influence of memory consumption even though I felt it shouldn't."

It's only the length of *property* names that have an affect on memory consumption, because properties are always loaded into memory.