Hi adobe-source-devel,
I've been using this patch for the last few months to write widgets
outside of ui-core. Is this okay to check into CVS? I can check in a
simple usage example, too. I'll also try and check in updates for the
FLTK ui-core implementation later this week (all radio_button_t
stuff).
Thanks,
Ralph
Index: headers/client_assembler.hpp
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /cvsroot/adobe-source/adobe-source/adobe/future/widgets/headers/c=
lient_assembler.hpp,v
retrieving revision 1.2
diff -r1.2 client_assembler.hpp
251a252,265
> typedef boost::function<void (const adobe::point_2d_t&, const adobe::exte=
nts_t&)>
> place_func_t;
>=20
> void
> utility_widget_place( place_func_t placer,
> const adobe::eve_t::calculate_data_t& calc,
> const adobe::eve_t::place_data_t& data,
> adobe::ui_overlay_t& overlay,
> adobe::ui_overlay_t::position_t node);
> /************************************************************************=
*************************/
> void
> utility_widget_calculate( adobe::extents_t& best_bounds=
,
> adobe::eve_t::calculate_data_t& geometry );
> /************************************************************************=
*************************/
Index: sources/client_assembler.cpp
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /cvsroot/adobe-source/adobe-source/adobe/future/widgets/sources/c=
lient_assembler.cpp,v
retrieving revision 1.2
diff -r1.2 client_assembler.cpp
3296a3297,3317
> void utility_widget_place( place_func_t pla=
cer,
> const adobe::eve_t::calculate_data_t& cal=
c,
> const adobe::eve_t::place_data_t& dat=
a,
> adobe::ui_overlay_t& ove=
rlay,
> adobe::ui_overlay_t::position_t nod=
e) {
> place_converter_result_t conv(place_data_converter(data));
>=20
> overlay.place(node, conv.first, conv.second);
> placer(conv.first, conv.second);
> }
>=20
> /************************************************************************=
****************************/
>=20
> void utility_widget_calculate( adobe::extents_t& bes=
t_bounds,
> adobe::eve_t::calculate_data_t& geometry ) =
{
> measure_extents_converter( best_bounds, geometry );
> }
>=20
>=20
> /************************************************************************=
****************************/
>
|