I got a mathematic script xxx.key but when i opened it with CDF reader.CDF reader shows tip "This notebook was created in a more recent version of Mathematica and is not compatible with this version of Mathematica. Contact Wolfram Research (www.wolfram.com) for upgrade information." But I have the newest version of CDF reader. what's the problem?
Related
Last year I got a PortJump packet from Codeweavers for an open source Windows software, not knowing that it uses Python 2.7 supplied by macOS < 12.3 only (Python 2.7 was marked deprecated by 2020 and Apple even announced that it wouldn't be included in the future anymore back in 2019.)
Termination Reason: Namespace DYLD, Code 1 Library missing. Library not loaded: /System/Library/Frameworks/Python.framework/Versions/2.7/Pyt
Referenced from: /Applications/EasyCash&Tax.app/Contents/MacOS/EasyCash&Tax
Reason: tried: '/System/Library/Frameworks/Python.framework/Versions/2.7/Python' (no such file)
(terminated at launch; ignore backtrace)
This means that every user updating to 12.3 won't be able to start the software any longer. What is the best approach to make the software run again on macOS (other than to pay Codeweavers some thousands of $$ again, just to move from the underlying Crossover 20 to 21 -- given that Codeweavers have replaced the Python 2.7 reference already in 21)?
To be more precise, any of these questions answered would help me:
Is there a chance to quickly replace the missing Python interpreter on OS level so the built-in Crossover would work again?
What steps need to be taken to include a Python 2.7 in the app packet, e.g. where is it referenced?
Is there an easy way to move to Python 3?
As I understand, Python is just used for the Crossover GUI, which isn't needed by my software. Maybe the Python reference can be removed alltogether?
(I'm not a Mac-native, so bear with me, if I'm missing the point.)
Got a patch from Codeweavers but the the difference is hard to spot as they just updated the Crossover version from 20.0 to 20.4, including a completely new wine version.
But I stumbled upon a note in the credits file about "the site module from python.org, modified to ignore /Library/Python". There seems to be an issue with python paths in MacOS as mentioned here btw.
Even if this answer may be not fully satisfying, maybe it helps someone. If you discover further details, please leave a comment.
I upgraded my machine from WinXP to Win7, and at the same installed Lattice Diamond 3.1. My more complex simulations hang, Active-HDL uses 100% CPU time and is obviously in an infinite loop. Stupidly I don't have the installation of Lattice Diamond 2.1 or 2.2, and unbelievably Lattice only allows you to download the latest version. No fallbacks!
Does anyone have an installation file for Lattice Diamond 2.1 or at a pinch 2.2? I can provide an FTP to put it on if some has. I know its a big file, probably 1G+.
Actually I was able to just copy the Active-HDL 9.2 directory from Win7 in a virtual box on another machine, and overwrite the Active-HDL 9.4 directory. I still wouldn't mind an old installation file but at least I can simulate now. And Diamond 3.1 its actually possible to eliminate bkm warnings and errors. There were 2 many bugs in 2.1, tech support actually admitted my warnings were Diamond bugs not flaws in my code.
Actually I found you can download older version from support -> Software archive
Actual link:
http://www.latticesemi.com/en/Support/SoftwareArchive.aspx
I am looking for an easy way to process images as an app on Mac – e.g. tracking moving objects, finding objects/faces etc.
This was inspired by a recent SO post: How to detect a Christmas Tree?
What is the best language for me to code this in, and how would I do it? I don't have any money to spend on software. I am also a complete beginner to image processing!
Thanks,
Fjpackard.
I would suggest to get openCV and connect it to Xcode. Numerous resources can be found on the web or in book stores.
See for example:
OpenCV MacOS installation
OpenCV and iOS
OpenCV and Xcode
OpenCV and Xcode
I think ipython notebook, and one of the the open source python distributions are two tools to look at. Also, there are some talks from PyData on Vimeo on how to do image processing with python based tool.
One of the python modules you can look at is called scikit-image.
The advantage of the ipython notebook is speakers often post their talks, so if they share their notebooks you can download them and follow along. I did that with one of the image processing talks from pydata and most of the code and images worked.
I downloaded the source code for the examples of the OpenGL superbible 5th edition from here:
http://www.starstonesoftware.com/OpenGL/
It was a file called XCode.zip
The projects there were actually never updated for the latest Xcode for OpenGL 3.0.
I wonder if someone already walked this perilous and dark way and made these projects work, or if there is a new zip file for the latest XCode.
The issue is that the examples use GLUT, which hasn't been updated to be able to use OpenGL 3 on OS X yet.
Apple didn't update GLUT. Trying to make time to adopt GLFW as the new framework.
— Richard S. Wright Jr., post on Twitter
I am facing an image processing task, and I'm using Python 3.2 (on a 64-bit Windows system). All my searches for image processing libraries have come up with are libraries for older versions of Python (most notably PIL, whose current version - 1.1.7 - supports Python 2.7). Does anyone know of an image processing library for Python 3?
By the way, I do not need fancy transformations and heavy stuff. All I need is to open a JPG file and get the image as an RGB-value matrix/list.
Any help will be most appreciated!
You can get a source version of PIL which will compile on python3.1 here:
https://github.com/sloonz/pil-py3k
also binary installer for 3.2 and 64-bit windows here:
http://www.lfd.uci.edu/~gohlke/pythonlibs/#pil
ref: Image library for Python 3
The world is changing and everyone seem to be moving to a brand new library: Pillow. It is a drop-in replacement for PIL but it is alive and does support Python 3.