On Fri, Oct 3, 2014 at 11:39 PM, Christopher Sean Morrison
wrote:
> The requirements for the web-based efforts on Github are not nearly as strict
> as they are for the main C/C++ sources. It's more important and useful to
> make sure your code is 100% self-consistent at a minimum, and ideally
Hi Albert,
On Oct 3, 2014, at 1:40 PM, Albert Coder wrote:
> Recently I had restarted working on Materials Database and had cleaned
> the code according to the guidelines in the Hacking file. But Hacking
> file is C / C++ centred and so for some PHP reference I saw the
> CIAnotify extension as it
Hello Sean,
Recently I had restarted working on Materials Database and had cleaned
the code according to the guidelines in the Hacking file. But Hacking
file is C / C++ centred and so for some PHP reference I saw the
CIAnotify extension as it is on BRL-CAD official GitHub. I have
observed the foll
>
> Is QTkMainWindow::event(QEvent *ev), the function you are talking about?
> I am not familiar with tcl/tk. Do I need to understand that before I
> should continue with the same?
>
Yes, that’s the function I was talking about. You don’t have to be familiar
with tcl/tk. I mean, at some point
>
> Correct me if I am wrong,
> Is "dm * qt_open()" the right function from where the tk window is
> being generated when we run "attach qt”?
>
Yes, you are right. In qt_open are created both the Tk window and the Qt one
which is embedded in the Tk one.
> Also can you tell what does "Tk_W
