[F/OS] Static Variable Extension || An extension for creating static variables in App

So @hammerhai , how much time should I post the use(reason) of this extension?


My extensions is never made for the use of only one person whether it is you or someone else.
I can’t leave the idea of ​​creating an extension if the extension isn’t usable for one.

What you think strange​:thinking:?

It depends on koder who use it. It can send the data through screens without saving it to any local storage. I would like to ask you that isn’t it better than a tiny db.

Really?
Are you serious do you think really it is possible with in built dictionary?. I don’t think.
It would be great if you do so with in built dictionary if you success then I want to request you to post here.

Dont take my words wrong. I just mentioned that you said and asked me. Stay calm because I haven’t said any bad word to you

And please now don’t spam this topic. I don’t wanted to let moderators to close it.

4 Likes

The reasons you listed are nearly all the exact same… You don’t have to use TinyDB and can use this extension through multiple screens without needing additional configuration, however, this extension isn’t good for any of those reasons since you can do the exact same with the TinyDB component.

I’m not saying it’s a bad extension, but there is no valid reasoning for why you came up with this?

TinyDB is good for long term usage where you need to access same data again and again but for short or one time usage this extension is fine.
TinyDB takes storage while this extension takes ram.

9 Likes

I’m already think before posting. Of course it will only work in screen1 but the text can still be sent to screen2 using this block:
blocks

i think strange because it’s too easy to make without having to use your extension :sweat_smile:

yeah that is better than tinydb but you can still use this one :
because this block will work without save the data to local storage.
blocks

Yeah it’s very possible, I will post here as soon as possible.

2 Likes

I mentioned that we can get data without using start value at my first post. I’ve been using that method till now. For start value, we should Make a list/dictionary of variables to a global variable and then pass it to the next screen which doesn’t look like getting variables easily and efficiently. Also, What if you don’t close the first screen and you want to transfer a variable back from the Screen2 to Screen1.

Eg. App (Screen1) > Settings (Screen2) - Here I only open the Screen2 and for returning back to Screen1 from Screen2. I just use close screen in Screen2. How can I transfer the variable to Screen1 using open with start value. This is a valid reason.

Sorry If I said anything wrong.

3 Likes

Take a look at this :


image

Same as :

blocks (6)


image

Same as :

blocks


image

Same as :

blocks (2)


image

Same as :

blocks (3)


image

Same as :

blocks (4)


image

Same as :

blocks (5)


image

Same as :

blocks (7)


image

Same as :

blocks (8)


image

Same as :

blocks (10)


image

Same as :

blocks (9)


Aia Project :

SimpleProject1.aia (4.2 KB)

5 Likes

You have valid points. They both work the same.

1 Like

Yup, thats right :upside_down_face:

1 Like

But, the only thing holds me from using dictionary is the start value. As you can see in my scenario

you make the dictionary variable on screen1 right?

Of course you can’t transfer variables from screen2 to screen1 using the
open with start value block, but instead, you can use these blocks to transfer variables from Screen2 to Screen1.

controls_closeScreenWithValue

component_event

How to use?

On Screen 2 do this :
blocks (1)

On Screen 1 do this :
blocks

3 Likes

:clap: Great! So, we can do all of these without using any third party things… Thanks for your idea.

1 Like

It’s my pleasure. :grin:

1 Like

You are a talented developer

1 Like

hi @dora_paz , May you please close this topic.
This topic contains mostly off topic posts. Just close the topic , do not unlist it

4 Likes

Closed at Op’s request

1 Like

You might want to reduce the icon size of your extension:

2 Likes

Topic opened at Op’s request

4 Likes