I don't see the problem.
Preferences is designed to be a simple API. You are asking to make it a
complex API with multiple configurations and points of failure.
Notice that you can easily implement your own Preferences API so I really
don't see the problem. It's not some low level API where
It's not so clean !! I don't understand why we couldn't manage multi
account preferences but one more time you purpose me a bypass as the
solution :(
On Friday, August 12, 2016 at 7:38:42 AM UTC+2, Shai Almog wrote:
>
> Hi,
> the API is designed to be really simple and a singleton. I
Hi,
the API is designed to be really simple and a singleton. I suggest using
Preferences.get(myUser + ".setting", defaultValue); etc... to provide user
specific settings.
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To
