This is really weird. I generate pdf using mpdf. I had no problem with printing pdfs. But suddenly this problem appeared. Not sure it is something to do with change of my code or updating my operating system or wireless printer printer.
System-------------Application-------Result
OS X 10.8.2---------Preview----------can't print
OS X 10.8.2---------Acrobat----------can print
OS X 10.7.x----------Reader----------can't print
Windows XP-----Reader/Dont know----can print
OS X 10.X.X---------Preview---------can't print
Some information:
We was able to print pdf before. There wasn't any complain from any OS/person.
I was working on some sql query changes. But I undo my things. still not working.
So what it says when someone try to print using "Preview"
-On my macbook pro it says (Printing - Connected to printing. and stays like this)
-Probably on other mac it also shows like happening something...but nothing happens.
FYI we don't get any confirmation like....printing completed....it is like printing..and printing.
There was a application PDFRepair. And after repairing with this application. I can print my pdf. But problem is its not freeware and quality is not good.
Maybe it is broken/damaged content issue.
Goal: Goal is print our pdf files with "Preview"
Any kinds of help or suggestions will be highly appreciated.
Finally solved. That was something to do with mPDF CMap resource stuffs. But it happens with only mPDF older version. In my case it was mPDF 5.0 Beta.
Using mPDF latest version will solve this problem. Now I can print my exported pdf from any OS and any application. Cheers
Related
I have an application with the following structure:
./Data/test.txt
./TestMacOSApp
So my TestMacOSApp opens ./Data/test.txt and uses the content of test.txt. This app was working for a long time either on my MacBook or others MacBook. Recently I noticed that the app works on my MacBook fine,
but on others it crashes throwing "File is not found exception".
I create TestMacOSApp using XCode v9.1.
MacOS version is 10.12.6.
The App creation steps are Archive->Export->ExportApp (Without re-signing).
Does someone else have such an issue?
How can I solve this issue?
I don't know how you open the file because you didn't provide the code which does this.
But I know that, when you export your app on other computers, it is important to calculate the real path with fullPathForFilename, instead of giving directly the path that you know. Like this:
auto fileUtils = FileUtils::getInstance();
string content = fileUtils->getStringFromFile(fileUtils->fullPathForFilename(filename));
Have you done this? If you have, and it doesn't work, your file is probably just not where you expect it to be, so please check again.
I am having issues getting lockPref working on my Mac. I have followed instructions here, as well as looking in other places for solutions. I have created a mozilla.cfg file, as well as a local-settings.js file in /Applications/Firefox/Contents/Resources/defaults/pref, as follows:
mozilla.cfg
//
lockPref("extensions.shownSelectionUI", true);
lockPref("extensions.autoDisableScopes", 11);
local-settings.js
pref("general.config.obscure_value", 0);
pref("general.config.filename", "mozilla.cfg");
These are both saved using Windows Latin encoding (have tried Windows Roman too). When opening Firefox, I am getting an error dialogue saying, "Failed to read the configuration file. Please contact your system administrator". I'm not sure where to go from here, as other solutions have involved UTF encoding problems and incorrect configuration values - I saved an empty mozilla.cfg file to attempt to rule that out, and the problem still persists.
FYI I'm using OS X 10.11.5 and Firefox 42.0. Thanks.
So, I didn't have mozilla.cfg in the correct location - I was storing it in the prefs folder with the local-settings.js, which is incorrect.
File locations are now as follows:
/Applications/Firefox.app/Contents/Resources/mozilla.cfg
/Applications/Firefox.app/Contents/Resources/defaults/pref/local-settings.js
I have a coworker who needs to have multiple versions of LabVIEW on his computer. He has a bad habit of opening LV2010 code in LV2013. LabVIEW doesn't warn that you are about to change all of the code to a new version of LabVIEW, and this breaks the code running on a test system on the production floor.
Here is my question: does anyone know of any kind of hack or legitimate method of changing the windows title bar for a single application? I would like to be able to change the color of the title bar only on LabVIEW 2013 from blue to red or something.
If this isn't possible, does anyone have an idea of how to distinguish one application from another that looks almost identical?
Thanks for any advice you have to give.
Well, the good news is that LabVIEW 2014 on will have the version number in their icon. That doesn't help your situation much, though. I'm not sure about changing the title bar, but I think I can help with your second question.
The icons for those versions are indistinguishable, however, the mass compile LabVIEW does when you open a project from an older version is a dead giveaway. You know LabVIEW is performing a mass compile if, while the project is loading, "Compiling:" appears where "Loading:" normally does. Close out of LabVIEW without saving and open the right version of LabVIEW. If he still goofs, there's always reverting in whatever version control software you're (hopefully) using, and you can always save back to older versions in LabVIEW itself.
I currently have four (older) versions installed to support projects that are under warranty. One trick I've found to be helpful is to put a .txt document in the same directory I save my .lvproj with the LabVIEW version as the title. For example, if the code is written in LabVIEW 2012 I include a text document called LV2012.txt in my _Project folder. Not a foolproof plan, but it has definitely made me double check my open version of LabVIEW before double-clicking.
I would suggest to use get VI version property described here: http://digital.ni.com/public.nsf/allkb/0C72D335AA87DD6486256FC40069C17F
Than using version information change you title bar text or transparency(I am not sure about color) or other FP component using VI ref property node.
I am trying to develop QRCode reader application in iPhone.
I am trying to use ZXing SDK. i have successfully run the sample application given by ZXing. But i ma trying to develope new application as per instructions in Readme given by Zxing. but when i am trying to add ZxingWidget in build phases. it going add but it shows like below
I think it will getting problem to me. When i am trying to run application it will give erros like Lexical or Prepocessor issue File not found.
Is am doing any thing wrong when am added to files to application.
Actaully first of all i added ZxingWidget.xcodeproj to my application by drag and drop. But it wont give any alert window would you like copy like similar when we adding images or files to xcode. and next i added cpp and iphone folders to xcode application. and later i added the frameworks as per read me.
Please any one help me in this issue.
Thanks in advance
Pretty hard to help without the real error message. In the Issue Navigator, you can Right Click > Reveal in Log to see the complete error that you can copy and paste.
That said, it sounds a bit like it can't find the headers (though I'm just guessing without the real error message.) If so, double check steps 4 and 5 of the readme.
if you run on real device, the problem will be solved.
I don't know the reason.
But I guess It's related to Build Products Path.
I have just installed VS 2005. I created a project. I added code to the project and then debugged the code. The program ran ok. I save the project. Everything saves fine. I go to open the project and the text editor is blank, or so it appears. After further investigation I notice that the code is there but I just can't see it. I debug and the program runs but no code can be seen. Strange. What is additonally weird, is I have installed the python idle and it to is blank, no code to be seen. However, the code is in there because I can run the code. I have adjusted just about every display property in VS as well as the os display props. I am using a Dell Latitude M60 Laptop, w/ windows xp professional, sp2, intel pentium M, 2 Ghz, 1gb ram. What do you think? Any body have this happen to them?
Could it be.. Right_Mouse+Click on the file in the Solution Explorer and chose "View Code"?
sometimes windows needs a restart :-)