Hi,
--- Roman Zippel <[EMAIL PROTECTED]> schrieb:
> Hi,
>
> On Sun, 24 Sep 2006, Karsten Wiese wrote:
>
> > Make sym_change_count static, implement
> > void sym_change_count_set(int)
> > and
> > int sym_change_count(void)
> > to set or get its value;
> > sym_change_count is only changed by void sym_change_count_set(int).
> > the latter can call a callback function, if a fn-pointer is set by
> > also new function
> > void sym_change_count_changed_set(void (*fn)(int))
>
> I don't quite understand the point of this. Frontends should only be
> interested in reading this value, wrapping this in a reader function would
> be fine. But what's the point of sym_change_count_set() and especially the
> callback?
>
enable/disable the qt- and gtk-gui configurator's
"save" toolbar-button/menu-entry.
The qt-configurator asks the user, if he want's to save the changed
.config if sym_change_count!=0.
So this patch replaces all occurances of sym_change_count manipulations
with calls to sym_change_count_set(), because
sym_change_count_set() calls back the *-configurator to let it update it's
"save"-widgets, thus reflecting the .config's dirty-state.
Nearly the same functionality could be achieved with a timer triggering 5/s
inside the qt/gtk-configurators.
mmmh, do you think, there are users, who prefer to be able to save an
unchanged .config, say to update it's file-times?
Karsten
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
kbuild-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
