Passing same Object through Activities












0














Im currently trying to pass the same Object trough an activity. What I mean with that is, that I don't want to create or clone the Object with the same attributes/values . (I don't want to create a new Object in the Heap, I just want to use the already existing Object from the passing Activity).



Is that even possible ?



I don't want to work with static objects either. I already tried the Parceable Interface (which is creating a new Object and not useable in my case)



intent.putParcelableArrayListExtra("items",allItems);
intent.putParcelableArrayListExtra("selected_items", selectedItems);









share|improve this question






















  • If all activities belong to the same app in the same process it can be done e.g. with a static member variable which holds the object (doesn't mean that it is recommended to do that at all).
    – Michael Butscher
    Nov 19 '18 at 21:17
















0














Im currently trying to pass the same Object trough an activity. What I mean with that is, that I don't want to create or clone the Object with the same attributes/values . (I don't want to create a new Object in the Heap, I just want to use the already existing Object from the passing Activity).



Is that even possible ?



I don't want to work with static objects either. I already tried the Parceable Interface (which is creating a new Object and not useable in my case)



intent.putParcelableArrayListExtra("items",allItems);
intent.putParcelableArrayListExtra("selected_items", selectedItems);









share|improve this question






















  • If all activities belong to the same app in the same process it can be done e.g. with a static member variable which holds the object (doesn't mean that it is recommended to do that at all).
    – Michael Butscher
    Nov 19 '18 at 21:17














0












0








0







Im currently trying to pass the same Object trough an activity. What I mean with that is, that I don't want to create or clone the Object with the same attributes/values . (I don't want to create a new Object in the Heap, I just want to use the already existing Object from the passing Activity).



Is that even possible ?



I don't want to work with static objects either. I already tried the Parceable Interface (which is creating a new Object and not useable in my case)



intent.putParcelableArrayListExtra("items",allItems);
intent.putParcelableArrayListExtra("selected_items", selectedItems);









share|improve this question













Im currently trying to pass the same Object trough an activity. What I mean with that is, that I don't want to create or clone the Object with the same attributes/values . (I don't want to create a new Object in the Heap, I just want to use the already existing Object from the passing Activity).



Is that even possible ?



I don't want to work with static objects either. I already tried the Parceable Interface (which is creating a new Object and not useable in my case)



intent.putParcelableArrayListExtra("items",allItems);
intent.putParcelableArrayListExtra("selected_items", selectedItems);






java android android-intent






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 19 '18 at 20:55









Ahmet KazamanAhmet Kazaman

350224




350224












  • If all activities belong to the same app in the same process it can be done e.g. with a static member variable which holds the object (doesn't mean that it is recommended to do that at all).
    – Michael Butscher
    Nov 19 '18 at 21:17


















  • If all activities belong to the same app in the same process it can be done e.g. with a static member variable which holds the object (doesn't mean that it is recommended to do that at all).
    – Michael Butscher
    Nov 19 '18 at 21:17
















If all activities belong to the same app in the same process it can be done e.g. with a static member variable which holds the object (doesn't mean that it is recommended to do that at all).
– Michael Butscher
Nov 19 '18 at 21:17




If all activities belong to the same app in the same process it can be done e.g. with a static member variable which holds the object (doesn't mean that it is recommended to do that at all).
– Michael Butscher
Nov 19 '18 at 21:17












1 Answer
1






active

oldest

votes


















0














You can only do so by using static objects(which you shouldn't) or by storing the object somewhere that is scoped at the application level and both activities can have access to (e.g. a singleton).



Writing to parcel/serializing and sending it through the intent bundle will create a new instance which is not what you want.






share|improve this answer





















    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53382496%2fpassing-same-object-through-activities%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    You can only do so by using static objects(which you shouldn't) or by storing the object somewhere that is scoped at the application level and both activities can have access to (e.g. a singleton).



    Writing to parcel/serializing and sending it through the intent bundle will create a new instance which is not what you want.






    share|improve this answer


























      0














      You can only do so by using static objects(which you shouldn't) or by storing the object somewhere that is scoped at the application level and both activities can have access to (e.g. a singleton).



      Writing to parcel/serializing and sending it through the intent bundle will create a new instance which is not what you want.






      share|improve this answer
























        0












        0








        0






        You can only do so by using static objects(which you shouldn't) or by storing the object somewhere that is scoped at the application level and both activities can have access to (e.g. a singleton).



        Writing to parcel/serializing and sending it through the intent bundle will create a new instance which is not what you want.






        share|improve this answer












        You can only do so by using static objects(which you shouldn't) or by storing the object somewhere that is scoped at the application level and both activities can have access to (e.g. a singleton).



        Writing to parcel/serializing and sending it through the intent bundle will create a new instance which is not what you want.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 19 '18 at 21:17









        Jorge GilJorge Gil

        367212




        367212






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53382496%2fpassing-same-object-through-activities%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

            SQL update select statement

            'app-layout' is not a known element: how to share Component with different Modules