-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Printable schema #760
Comments
Seems like a good feature to have. @chrisjlocke So.. this might be a good starter project for your C++/Qt learning? 😄 |
Oh crap.... 😉 |
Nice, that is a good start to my earlier schema diagram request. |
This is, more or less, one of the points that I've implemented so far for my issue #1525. The output is very simple, but it may fit your needs. @chrisjlocke, if you'd like to try, it's already in the nightly build. |
I downloaded 180927 nightly and nothing happens when I click 'Database Structure - Print'? |
Ditto - nothing happens at all if I select 'Print' from any context menu. |
Weird... Maybe we are affected by this Qt bug But it should be fixed in QT 5.2.1, if I understand it correctly. |
Ok, can you bypass the print step and just export the canvas to an image and display it within the DB4S gui? |
This adds a print preview step before printing in the Database Structure tab. This is nice to have, but it also aims to work around the problem found in Windows, reported at issue #760.
Let's try with a Print Preview Dialog instead of a Print Dialog. Maybe it works around the problem and nevertheless, it's nice to have it. I've changed only the Database Structure tab for the moment. Could you test it again with tomorrow's nightly build? |
I've reproduced the problem under Windows. At least the print preview version works until you press the Print icon; then only the PDF export is possible, the print dialog for choosing printers, PDF format and print settings doesn't show up. It seems that Qt has portability problems in this regard. I'll use the print preview in all the scenarios and at least we'll have PDF support. |
Reading the linked bug report:
I see that we distribute a Qt5PrintSupport.dll file, but no printsupport folder. Reading Qt for Windows - Deployment
@justinclift, can the printsupport plugin be distributed inside the nightly build? I guess that will solve the problem. This is similar to the image-formats case that you already solved, isn't it? |
@mgrojo There's only one dll (windowsprintersupport.dll) inside printsupport folder. Do you mean adding this file? |
@karim I suppose we have to add the complete folder with whatever it contains. If there's only that file inside, I guess that is the only one needed. |
Yes, there is only one file in my Qt 5.7.1 installation. I just added it. |
Great. That should work. Let's see with tomorrow's nightly build. |
Tried latest nightly and the print action only creates a tabular listing of my database? |
Details for the issue
I know the 'Database Structure' shows the database schema, and I print this out a lot when working on various databases. I work in Windows, so its easy to do a printscreen, slap it in Word or something, and print it out. However, one of the systems I'm working on is 17 tables, with one of these having 17 fields. Nothing 'major', but it means printing it from the 'Database Structure' is a pain. I use PicPick to help print scrollable windows, but it struggles on Qt widgets, so can't be used with DB4S.
In desperation, I knocked something up in VB.
This pulls in the database schema and creates a form of treeview controls. Its still manual, as I have to 'screenshot' it still, but PicPick is able to scroll it for me and capture it as one image. It also fills the page left to right, rather than the 'Database Structure' view, which for me, is just one long column - not efficient with paper usage.
Requirements for this for other users might be low, so just 'throwing it out there' to see what others think, but a schema view thats printable could be quite useful.
Useful extra information
I'm opening this issue because:
I'm using DB4S on:
I'm using DB4S version:
I have also:
The text was updated successfully, but these errors were encountered: