It can appear to be a bit crazy but I'm doing this because on some applications I have the need to have the same database field presented on more than one widget on the same window/group, also more than one filed with the same name but form different tables, I'm using the widget name as a hint for the table/field name used. With this schema I can have some flexibility to name widgets to satisfy the compiler and other developers/designers and still ensure where the meaningful piece of information is.
En 22/12/2010 01:50:16, Domingo Alvarez Duarte <[email protected]> escribió: > I tested with only changing the string constants on the patch from > "@name" to "$(name)" and "@class" to "$(class)" and it seems to work > fine till now, again as I pointed out it's a simple text replacement. > > The other part I didn't submitted because I don't think it'll be > accepted but for my own I also accept "@" as a separator on the widget > name field like "d...@colors@depth" this string end up on generated > source code as "dbf_color_depth" but I can retrieve it as a macro > "$(dirty_name)" and I'm using like this: > > =o->user_data((void*)"$(dirty_name)"); > > To get: > > o->user_data((void*)"d...@colors@depth"); > > And with that I can split and extract several meanings from it. > _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
