Viktor Szakáts wrote:
>
> Here I still wonder if it's normal to have such
> large central/global conditional constructs with
> many hard-wired logic which really belongs to
> other/different parts of this package.
>
> Isn't there a more generic, or modular solution
> to this problem?
>
Modular and grandular approach is always desirable.
But "how to" in case of hbqt_hbslots.cpp is elluding me.
The reason is how to call single function on PRG level.
Signals and slots are designed to to call a central function
based on the type of arguments. If we try the other way
each method in classes on TQ*.prg will have to implement
a separate function matching the type.
I am sure I could not explain myself clearly. Please understand
my contents.
-----
enjoy hbIDEing...
Pritpal Bedi
_a_student_of_software_analysis_&_design_
--
View this message in context:
http://n2.nabble.com/SF-net-SVN-harbour-project-13952-trunk-harbour-tp4609995p4613747.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
