Subject:
|
Re: LDView 3.1 on Mac OS X!
|
Newsgroups:
|
lugnet.cad.dev.mac
|
Date:
|
Wed, 21 Feb 2007 18:40:35 GMT
|
Viewed:
|
12247 times
|
| |
|
|
In lugnet.cad.dev.mac, Travis Cobbs wrote:
| |
In lugnet.cad.dev.mac, Jim DeVona wrote:
| |
On my MacBook, wchar_t is a 4-byte type. I’m not sure about the QChar
definition. I’ve found a class definition in
/src/corelib/tools/qchar.h/.cpp, but my C++ is weak so on first glance I’m
not sure how to interpret its type compatibility.
|
I took a look at the QChar docs in both QT 3 and QT 4, and updated the
failing line of code to call the unicode() function on the QChar object.
This builds fine in QT 3, and should also build fine in QT 4. I haven’t had
a chance yet to see if it actually works as expected, but I don’t see why it
wouldn’t. (The only way to be sure it works is to use a non-English language
setup in LDView and verify that the special characters display correctly.)
Note that while I have committed the change to cvs, it takes a while for the
change to propogate to the anonymous cvs. I don’t know how long it takes,
but it’s no more than 24 hours.
|
Hi, Travis. I’ve
built LDView 3.2 with Qt 4.2.2 using your updated code. I thought I’d share my
leads on the remaining kinks before proceeding.
First, how I got it to compile:
- I expanded libtool to /usr/bin/libtool at line 13 of Makefile.inc just because I have another libtool in /usr/local.
- I expanded lrelease to ${QTDIR}/bin/lrelease at line 57 of QT/LDView.pro just because I haven’t added the Qt bin to my path.
- I updated VERSION to 3.2 at line 109 of QT/LDView.pro (just because).
More essentially,
- I inserted “@$(CHK_DIR_EXISTS) LDView.app/Contents/MacOS/ || $(MKDIR) LDView.app/Contents/MacOS/ ;” before the cp commands at lines 113 and 116 of QT/LDView.pro and appended a slash / to those cp targets. The latter change causes the support files to be copied into /MacOS instead of as /MacOS, and the additional commands make sure that the /MacOS directory exists (since these commands are prerequisites for the main $(TARGET) which is where /MacOS was previously created).
- Changed QPopupMenu near line 1313 of QT/ModelViewerWidget.cpp to Q3PopupMenu and inserted #include <q3popupmenu.h> at the top of the file.
| |
| |
| |
I’m glad that Bricksmith can make use of them. Does it have a UI to add
new directories to the part search path?
|
Nope, so I had feared it might not be able to access them. However, I’ve
checked and Unofficial is hard-coded as the unofficial parts directory
name (in Source/Other/MacLDraw.h, for those following along at home). You
can set the LDraw directory, of course, so it will just look for an
“Unofficial” directory within that.
|
Interesting. I wonder if it was just a coincidence that we both chose the
same hard-coded directory for Unofficial parts, or if Bricksmith’s author saw
that I had used it. I suspect the former, since LDView didn’t work on the
Mac.
|
Well, there was the 1.0 version, but I don’t think it used Unofficial, either.
At any rate, I am glad it is a convention of sorts.
| |
| |
In fact, the menu bar and Dock do not remain visible in full screen mode
with this build, so it really is “full screen” (barring the border - which I
suspect is the sort of thing that could probably be eliminated with some QT
4 style property).
|
That’s good. I guess now I just have to figure out why it’s drawing that
really large border across the top and the relatively large border around the
other sides.
|
I suspect I’ve found a clue.
Here is a log of warnings from my build. There are a number of uic3 warnings
about unsupported properties such as WinPanel, Sunken, and NoFrame. I
turned up this document
about porting Qt 3 to Qt 4, which I haven’t looked at very closely yet, but it
may explain either equivalent new values or how to incorporate Qt 3 backwards
compatibility (like the q3popupmenu.h fix I stumbled upon above).
| |
| |
| |
| |
- I can’t seem to invoke “Fly Through” mode - the menu item becomes checked appropriately, but the status bar continues to read “Examine” and none of the fly through controls seem to be active. (In other words, except for the menu indicator, it remains in “Examine” mode.)
|
That’s very odd. It works fine in the version I compiled.
|
OK.
|
It could be that that was broken in the Linux QT version of LDView 3.1, and
is fixed in the 3.2 code-base.
|
Well, it’s still not working in my 3.2 build with QT 4. This leads me to think
that it is a QT issue, so I may end up trying QT 3 after all if a QT 4 culprit
can’t be found.
| |
Scroll wheel support failed to make it into the QT version until after the
3.1 release. It was something I noticed after I started using the QT version
more heavily. It’s in the 3.2 code-base. (It even works with the Macbook
touch pad when you use two fingers and move up and down.)
|
Confirmed. Awesome! (I love finger scrolling.)
Other bugs (possibly things you’re just working on, since it hasn’t been
released yet anyway):
- The “camera” drop-down menu button in the toolbar doesn’t do anything. Possibly another QT3/QT4 issue alluded to among the build warnings given above.
- The “Part List” export is nice, but the “Column Order” part of the dialog is unlabeled and seems to duplicate the whole list as another column for each checkbox rather than select which columns to include in the list. (Just checking one of the boxes makes it come out fine, but there are a lot to uncheck!)
- Minor thing: some preference dialog panes look a little crowded at first, but look just fine if you resize the dialog a bit. Actually might be due to the same big border style as the main window.
Also, both the “Open Recent” popup menu and printing work fine.
Be well,
Jim
|
|
Message has 1 Reply:
 | | Re: LDView 3.1 on Mac OS X!
|
| (...) After taking another look at the list of uic3 warnings and LDView.ui, I am willing to bet that my problems with fly-through mode - and polling mode, maybe are due to QT4 differences. Both pollChanged(QAction*) and viewChangedMode(QAction*) are (...) (18 years ago, 22-Feb-07, to lugnet.cad.dev.mac, FTX)
|
Message is in Reply To:
| | Re: LDView 3.1 on Mac OS X!
|
| (...) I took a look at the QChar docs in both QT 3 and QT 4, and updated the failing line of code to call the unicode() function on the QChar object. This builds fine in QT 3, and should also build fine in QT 4. I haven't had a chance yet to see if (...) (18 years ago, 20-Feb-07, to lugnet.cad.dev.mac, FTX)
|
39 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
