Vlad, Gurjot,
If you are still interested in doing Qt work with BRL-CAD, you might
want to take a look at the prototype work in the brlcad-qtged branch,
src/qbrlcad directory. I don't have any of the display manager logic
hooked in yet, but if you would like to try hooking in the Qt and/or
osgl d
On Sun, Nov 9, 2014 at 4:44 PM, Vlad Bogolin wrote:
> Hi,
>
> I have a question regarding the whole command interpretation. After looking
> in mged's code I found out that the command is build character by character
> (mged.c/mged_process_char) but I've been struggling for a while to find what
> h
Hi,
I have a question regarding the whole command interpretation. After looking
in mged's code I found out that the command is build character by character
(mged.c/mged_process_char) but I've been struggling for a while to find
what happens after the command is complete. I mean there is a call to
> Hey guys,
>
> Is there any working currently ongoing with the Tk->Qt effort?
>
Hi,
Yes, I am currently working but unfortunately I only had time to do a little
bit more research and I found out that I was thinking at an approach that isn’t
suitable. So, what I have in mind at the moment is
On 30-Oct-2014 7:39 pm, "Clifford Yapp" wrote:
>
> On Fri, Oct 3, 2014 at 6:16 AM, Vlad Bogolin
wrote:
> >
> >>
> >> 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 sam
On Fri, Oct 3, 2014 at 6:16 AM, Vlad Bogolin wrote:
>
>>
>> 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 do
>
> 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
On 26 September 2014 23:54, Vlad Bogolin wrote:
> Also, if you have any questions regarding the current implementation feel
> free to ask.
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"?
Also can you tell
On 26 September 2014 23:54, Vlad Bogolin wrote:
> Yes, you are right. If you look in the libdm/dm-qt.cpp you should find a
> section where when a Qt event occurs a corresponding Tk one is generated. So,
> basically in order to have just a Qt window, we have to replace the whole Tk
> event handl
Hi,
> On 25 sept. 2014, at 22:24, Gurjot Singh Bhatti
> wrote:
>
> @Vlad
>
> Hi,
> I just compiled qtged branch on my system. Now I see that the Qt
> Display Manager is not embedded in the Tk window. So now we are
> looking at replacing Tk window with Qt one right?
Yes, you are right. If you
@Vlad
Hi,
I just compiled qtged branch on my system. Now I see that the Qt
Display Manager is not embedded in the Tk window. So now we are
looking at replacing Tk window with Qt one right?
I am very much interested to contribute to this. If you could share
your ideas on how to approach this it'd
12 matches
Mail list logo
