ilan Expert Licensed User Longtime User Dec 24, 2017 #1 hi i have sometimes a snipped or a code that i dont need for now but maybe will need later so what i do is i comment it and move it to the bottom of the Page. it would be nice that if i then want to add a new event for a button or anything else from the designer that it will be added before all commented text. so a simple check if there is ONLY commented lines on the bottom then ignore then and add the event before them. this will save me the cut/paste for each new event added from the designer thank you, ilan
hi i have sometimes a snipped or a code that i dont need for now but maybe will need later so what i do is i comment it and move it to the bottom of the Page. it would be nice that if i then want to add a new event for a button or anything else from the designer that it will be added before all commented text. so a simple check if there is ONLY commented lines on the bottom then ignore then and add the event before them. this will save me the cut/paste for each new event added from the designer thank you, ilan
LucaMs Expert Licensed User Longtime User Dec 25, 2017 #2 I would prefer that the default activity code had a structure similar to this: Code: ... ... #Region VIEWS' EVENTS #End Region #Region METHODS #Region PUBLIC METHODS #End Region #Region PRIVATE METHODS #End Region #End Region #Region OTHER EVENTS #End Region and that the event routine created by Designer was placed after the last routine in the VIEWS' EVENTS Region (This is not a my wish; I'm saying that yours, @ilan, is very personal, according to your "tastes". Also, my example is more similar to the structure that I give to my classes, because an activity does not have real public methods, even if they can be called via callsubdelayed) Last edited: Dec 25, 2017
I would prefer that the default activity code had a structure similar to this: Code: ... ... #Region VIEWS' EVENTS #End Region #Region METHODS #Region PUBLIC METHODS #End Region #Region PRIVATE METHODS #End Region #End Region #Region OTHER EVENTS #End Region and that the event routine created by Designer was placed after the last routine in the VIEWS' EVENTS Region (This is not a my wish; I'm saying that yours, @ilan, is very personal, according to your "tastes". Also, my example is more similar to the structure that I give to my classes, because an activity does not have real public methods, even if they can be called via callsubdelayed)
