That way it’s aware of the variables from file that includes it.

Not WordPress standard practice (but then you are still using include in the template part anyway) but seems a lot more sensible than loading a template part and then loading the file that included it again. Infinitely loading files within themselves could lead to a lot of issues. At least consider using include_once instead of include.

SET THE VARIABLES:

$options = array( ‘option1’ => ‘value1’, ‘option2’ => ‘value2’ );
set_query_var( ‘my_options’, $options );
get_template_part( ‘templates/example/part’ );

RETRIEVE THE VARIABLES IN TEMPLATE PART

$options = get_query_var( ‘my_options’ );
if ( is_array( $options ) ) { extract($options); }
echo ‘This is my option 1 value: ‘. $option1 .”;
echo ‘This is my option 2 value: ‘. $option2;

…and just my two cents for theme authors. I think that the locate_template function suggested in this article is not the expected choice to include a template part. You might get the same result using it, nevertheless it does not provide the extra do_action trigger that get_template_part does…and some plugins might rely on it. In addition, using an include() function for your template parts will produce several alert notices on several quality review tools ( such as the Theme Check plugin ).

Thank you. I think this is a better solution that the one provided by this article.

in template part:
global $r;
echo $r;
it will work fine

This is really the way to do it properly.
Don’t use `include()`!

To get the variable, use get_query_var().