从 OSF/Motif 迁移Xt 到 GTK+
我有一个名为 XClient 的类，它是用 Xt（X Tools Intrinsic 库）编写的，用于设置多插槽连接。该 XClient 类旨在供 OSF/Motif GUI 扩展 XClient（以便 GUI 可以在套接字上进行通信）。
我正在尝试迁移到 GTK+ 环境，出于可移植性原因，该环境不使用 Xt 库。是否仍然可以创建一个包装器以允许 GTK+ 使用 Xt 库调用，或者这是不行的吗？
I have a class called XClient written with the Xt (X Tools Intrinsic library) to setup a multisocketed connection. This XClient class was meant for OSF/Motif GUIs to extend XClient (so the GUI could talk on sockets).
I am trying to migrate into a GTK+ environment which does NOT use the Xt library for portability reasons. Is it still possible to create a wrapper to allow GTK+ use Xt library calls or is that a no no?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我不希望 Xt 和 GTK+ 能够很好地工作，或者根本不能在同一进程中工作。他们都试图“拥有”X 显示、主事件循环等。
I wouldn't expect Xt and GTK+ to work well or at all in the same process. They are both trying to "own" the X display, the main event loop, etc.
您应该能够通过调用 XtAppInitialize() 来独立于 GTK 运行 Xt，这将打开它自己与 X 服务器的连接，从而将两者视为独立的客户端。
您可以通过在单独的线程中调用
XtAppMainLoop()来处理单独的事件循环。请注意，不要尝试从该线程以外的任何地方对其执行任何操作，因为我不确定 Xt 是否是线程安全的。 （现在可能是这样了；我已经有近 20 年没有与 Xt 分开了，而且那时候也不是。）You should be able to run Xt independently of GTK by calling
XtAppInitialize(), which will open its own connection to the X server, which will treat both as independent clients.You can deal with having a separate event loop by putting the call to
XtAppMainLoop()in a separate thread. Just be careful that you don't try to do anything with it from anywhere other than that one thread, because I'm not sure Xt is thread safe. (It may be by now; I haven't had Xt apart in almost 20 years, and it wasn't back then.)