seems like an extra deferral

@carlw Did he actually do that? In that case, yes absolutely.

Ah, of course!

Sorry, I was thinking of another issue, but you're right, that's what's happening here.

@edvin Deleted a few messages...i'll try to reproduce if I get a chance and take it from there. What do you think about an onSucceeded parameter and an onFailed parameter? That way you can use the same delegation as in your implementation of call().

@carlw Thanks! I will look more at this tomorrow and try to figure out what the best way to do this is.

Is the preferences storage persistent ?

val preferences = Preferences.userRoot().node("app") //Setting Access Token fun setToken(token : String) { preferences.put(TOKEN, token) } //Getting Access Token fun getToken() : String { return preferences.get(TOKEN, null) }

yes

it will store automatically

Are you sure it works in different windows system

?

I tested it on windows, mac and linux

@ron uploaded a file: Untitled

this is how I use it

The builtin java preferences seems to have issues on some versions of windows. if i run the app on windows 10 it just gives me registry permission errors and doesn't work

Strange as I use that code on windows 10

what is the registry error

something like this

WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs 
at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5.

Yes looks similar

I had that error with running java itself, I fixed it by creating a registry key, let me see if I can find that error again

Okay

by following that issue, I solved my problem

that's a bad solution, we can't require users to add registry keys

well aparently its a known java issue

Well, i would prefer keeping the data out of the registry. it makes it much easier to debug if there's just a simple config file that can be viewed instead of having to search inside regedit

you can do that with tornadofx too, using the config object

Link ?