QModelIndex problem!

[landonmkelsey]

The point here is to learn something!

If I had surrendered/redesigned every time I ran into a problem, I'd never have learned anything!

The code is unimportant here since my ultimate aim is to incorporate the bridge pattern. Ultimately the user will be able to choose the means of server concurrency
via the bridge pattern. In C# this is straightforward!

My code in C# is a great testament to the value of patterns!

Redesign? Why? The user chooses ultimately!

I started out trying to incorporate Qt4 for gui into my already running program!

The means of concurrency in TCP/IP is controversial anyway!

See great work of the deceased W Richard Stevens! www.kohala.com

[wysota]

The point here is to learn something!

If I had surrendered/redesigned every time I ran into a problem, I'd never have learned anything!

You would learn to avoid bad designs and create good ones.

Redesign? Why? The user chooses ultimately!

Because the solution is neither scalable nor modular nor straightforward.

I started out trying to incorporate Qt4 for gui into my already running program!

So what's keeping you from rewriting some parts of the application to simplify the overall solution instead of wrestling against problems related to mixing two different technologies that only need a minor change to interoperate perfectly?

The means of concurrency in TCP/IP is controversial anyway!

I'm not sure what you mean here, but there are numerous designs related to obtaining concurrency in TCP connections - just look at available operation modes of the Apache webserver. If you want multithreading, you are welcome to use it but do it properly, for example by using a thread pool to keep resource usage at a reasonable level while keeping your system responsive.

[landonmkelsey]

the main point is !

My C# code uses a bridge pattern to allow the user programmer to select which "client handler" he/she wants/supplies! One can choose the thread pool or 1 client one thread generated on "call-in"

One may even choose an iterative server!

I wanted to generate C++ code to do the same thing! Since C++ does not have an "interface", I would have to use an ABC!

I'll solve the problem myself! Thanks for your help!

I quess C++ will wither and die! : ( as Java and VB)

done!

[jacek]

Since C++ does not have an "interface", I would have to use an ABC!

You don't need a separate keyword for everything. An interface is a special kind of ABC.

[wysota]

My C# code uses a bridge pattern to allow the user programmer to select which "client handler" he/she wants/supplies! One can choose the thread pool or 1 client one thread generated on "call-in"

I quess C++ will wither and die! : ( as Java and VB)

The language used is independent of the design. If you have some design in C#, you can implement the same design in other languages.

On the other hand a bad design is bad independent of the language used to implement it.

You are trying to bridge two technologies that use different concepts. This is possible but prone to errors and that's exactly what you are experiencing. So you can either struggle with that or change one of the concepts.

As for interfaces - interface is an abstract term. Each class is an interface, a class containing virtual methods is an interface that can be realized in different ways by more than one class, a class containing pure abstract methods is an abstract interface that has to be implemented by other class(es) (an ABC).