Thanks for the link !

Yes it is, but I just saw I misunderstood how you used it. There's been cases where developer gave the Qt installation QML path. Can you share your QML imports ? There might be something there that could be useful to understand why not everything needed was included.

Take a look at QtRPT print report engine and QtRptDesigner. May be it help you. You can fint QtRPT at http://www.qtrpt.tk

@VRonin Thank you for your suggestion! Interestingly that doesn't have any effect. The application still uses the unified menubar. I set the attribute like this in my main() before I construct and show the QMainWindow: QCoreApplication::setAttribute(Qt::AA_DontUseNativeMenuBar, true); Interestingly I get the following debug messages in the application output pane when opening and closing the application when the attribute is set to true: Menu item is already in a menu, remove it from the other menu first before inserting Menu item is already in a menu, remove it from the other menu first before inserting Menu item is already in a menu, remove it from the other menu first before inserting Menu item is already in a menu, remove it from the other menu first before inserting Item to remove does not belong to this menu Item to remove does not belong to this menu Item to remove does not belong to this menu Item to remove does not belong to this menu I also tried QMainWindow::setUnifiedTitleAndToolBarOnMac() but without any success either. The application still uses the unified toolbar. I'm using Qt 5.6 on OS X 10.11.4 (El Capitan)

@SGaist It's a bit inconvenient because it causes a new terminal window to open every time. I'd prefer to have just one window that all of my app's output goes to so I can place it in a specific spot. I see that, behind the scenes, Qt Creator is calling a bash script that executes some AppleScript to get the terminal window to open. I may try tinkering with it to see if I can get it to behave how I want, but it'd be much more convenient if Qt Creator allowed breaking off the Application Output (and the issues section now that I think about it) into its own floating window so that I can make full use of the vertical real estate of my screen.

@pavel_abr Did you solve this? Please let me know the solution.

@patrikd Thank your suggestion worked fine for my framework too. Wish I could give you a cartload of reps for that :-).

Hello, That not the problem here. If i understand correctly, the OSX Application Menu is translated by Qt, not my application. The problem occurs only with QtQuick and on a OSX no-english. So why i must do give a translated file created by me for QtQuick and not for QtWidgets ? (And not the translated files qt) Regards, nelbok

Please have some patience, this forum is community driven and not all users live in the same timezone as you. The picture you are linking to doesn't show a hovered button but a checked button. You will have that visual effect if you set the checkable property of the action to corresponding to the button as true and you check it.

Thank you for the hint about 'solved'.

@DRivkin anyone interested can send an email to jobs@next.audio and I can take it from there.

Update: I managed to get a QWindow involved into the code, yet the toolbar is messed up. Screenshot New code: void Test::createFancyMacWindow() { QWindow* w = new QWindow(); NSView* mainWindowNSView = (NSView*) w->winId(); NSWindow* window = [mainWindowNSView window]; NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init]; // move toolbar where the titlebar used to be [window setTitleVisibility: NSWindowTitleHidden]; // Adjust Cocoa layouts NSView *contentView = [window contentView]; [contentView setAutoresizesSubviews:YES]; QMacNativeWidget *nativeWidget = new QMacNativeWidget(contentView); //nativeWidget->move(0, 0); nativeWidget->setPalette(QPalette(Qt::red)); nativeWidget->setAutoFillBackground(true); NSView *nativeWidgetView = nativeWidget->nativeView(); [contentView addSubview:nativeWidgetView positioned:NSWindowAbove relativeTo:nil]; [nativeWidgetView setAutoresizingMask:NSViewWidthSizable | NSViewHeightSizable]; [nativeWidgetView setAutoresizesSubviews:YES]; nativeWidget->show(); // Show the window. [window makeKeyAndOrderFront:window]; [pool release]; QMacToolBar *toolBar = new QMacToolBar(); toolBar->addItem(QIcon(), QStringLiteral("Helloooo")); toolBar->attachToWindow(w); [window setToolbar: toolBar->nativeToolbar()]; w->show(); }

nevermind, i saw someone had a different error but adding QMAKE_MAC_SDK = macosx10.11 in the pro file also fixes this.

Core i5 is for sure x86_64 and it can execute i386 binaries as well. Because x86_64 was invented by AMD and later implemented by Intel as well it is often called AMD x86_64.

Sounds good :)

Then you can use that knowledge to add OS X to the backend list

Sorry, I've haven't given enough info: it's working on 10.8.5 with a Qt 5.6 build

Thanks for the help. But the real reason was that, I was using wrong version of QT for my project. My project supports QT version upto 5.4 & I was using 5.5. After downgrading all works fine now.

The latest development is that I had over 254 files open at once. No wonder nobody else had encountered this.

Disregard my previous post, cookies policy can be set in the QWebEngineProfile owned by the QWebEnginePage owned by the QWebEngineView, like this: ui->webView->page()->profile()->setPersistentCookiesPolicy(QWebEngineProfile::NoPersistentCookies); The page pointer remains the same for my purposes, at least.

Thanks so much for taking a stab at it. I tried setting the experimental.preferredMinimumContentsWidth to numbers ranging from 1 to 10000, but it doesn't seem to have any sort of affect for me. I have tried playing around with experimental.page.scale. I found setting it to 1200/webview.width gives something similar to what I'm looking for. It prevents the page from shrinking when resizing. However, everything ends up getting very blurry, so it can't be a solution for me. I'll try digging through the experimental settings some more. It's too bad that it isn't better documented. It is so sad that this zooming "feature" can't be turned off. It looks like QWebView behaves properly by default, but it is a Qt widget, not a Qt Quick widget. So I won't be able to use it in my application. If anyone out there knows how to fix this, please help!

Issue created at QTBUG-47390

Thanks a lot! This hint was expedient.

Thank you, turned out it could be done like this: QMAKE_POST_LINK += $SCRIPT_PATH $ARG1 $ARG2 No need for system()

Thanks for the help all, Im a noob and realized im working in an IDE like Xcode that makes apps. I followed this tutorial for good info: https://www.youtube.com/watch?v=6KtOzh0StTc Thanks again!!

Hi and welcome to devnet, I'd recommend taking a look at the bug report system to see if it's something known

Hi and welcome to devnet, Did you install the MySQL client libraries on your OS X using e.g. macports or homebrew ?

Hi, You can try to create your own style based on QMacStyle. Hope it helps

Can you try to comment the line OpenFile(filename); and use a qDebug there instead, this function could be the problem Thanks

Hi and welcome to the devnet, I use protobuf too (in Windows, Linux and OSX). In our OSX environment we build protobuf with $PROTOBUF_SRC_DIR/configure --silent --prefix=$PREFIX --disable-shared --enable-dependency-tracking=no

Hi and welcome to devnet, As an example, you can take a look at the QtMacExtras module. The code there uses Objective-C++ to create interfaces to use OS X native frameworks.

Ok, thanks :).