Hi Pritpal, > Log Message: > ----------- > 2010-01-08 15:44 UTC-0800 Pritpal Bedi (prit...@vouchcac.com) > * contrib/hbqt/hbqt_hbslots.cpp > ! Fixed a very bad omission : > if( object->property( signal ).toInt() == i ) > => > if( object->property( signal ).toInt() == i + 1 ) > It fixes if an action is not already defined for a widget. > TO WATCH: Is is desirable ? > > * contrib/hbxbp/xbpfiledialog.prg > ! Small optimization. > > * contrib/hbide/hbide.prg > * contrib/hbide/ideactions.prg > ! Separated toolbar and menu actions, the whole point of > recent reported issues, because toolbar and menu implementation > call different methods with different intensions. > > Please test if toolbar and menu option behave correctly. > > GROUP DECISION: should I go for QProcess() to manage build phase > or keep Harbour centric implementation as well ? Qt seems to be > proper choice under this context.
My vote is to use Harbour core functions if they are available. It's a much better investment, and in case something is missing we can extend core and everyone benefits. On the other hand I see no point in investing in parallel features. (see discussion for yesterday, I could only guess in a few cases, since QProcess is a totally unknown a new area, while Harbour core process management has been discussed many times and several good examples are available. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
