> On Friday, October 07, 2011, Tom Breton (Tehom) wrote:
>
>> How are these classes best fit into files?
>
> In my opinion, you can never go wrong putting every class in separate
> .cpp/h
> files, and always putting implementation details in the .cpp file, no
> matter
> how trivial they are.
Understood. Seperate they will be.
> So having said that, I wouldn't be especially worried about dumping 12 new
> files in whatever directory the parent they were forked out of was
> located,
> but neither would I object to creating a new subdirectory. It's all good
> either way.
I'll put them into their own directory.
> I'll probably end up using QObject::tr() to get those translations
> working,
> but you and everybody else can just leave that junk to me. I ask
> everybody to
> wrap their user-visible strings in simple tr() calls, but I don't expect
> anybody to worry about it beyond that.
Thanks for the advice. But Qt wants all "tr" calls anchored in some
Qt-derived class. There is no bare "tr" call. So having moved them into
new classes, any direction I go has an impact.
So I'll take the most conservative approach and anchor them where they
originally came from, EventParameterDialog.
Thanks,
Tom Breton (Tehom)
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
