I have a Meteor 1.3 and my client/main.less file is not being imported. My expectation is this should be happening by default. I have the less Meteor package installed.
Interesting enough, client/main.scss IS being imported. Why would that happen if I have the less package installed?
Any ideas?
It sounds like the file isn't being loaded for some reason. Perhaps there is an error in the file that prevents inclusion, but is somehow not reported.
Try replacing it with a small file with a very noticeable result (like changing the page background colour to something bright)
Related
I have been beating my head for the last 7 hours on this. Full disclosure, I am a PHP guy and not the strongest at ASP.net. So I am coming to you experts.
The issue is that when we run the code below it will product a valid PDF if we use the MSHtmlEngine function (which sets EngineType to MSHtml), but it won't work with the GeckoEngineOptions (which sets EngineType to Gekco). The problem is that the MSHtml won't generate the SVG graphics, so we need to run the Gecko method. When we run the Gecko method, it produces this error:
"ErrorMessage":"Failed to find ABCGeckoWP.exe."
However the file is in the output directory ("bin/"), as well as the project directory. The XULRunner38_0 also appears to be right as well in both the project and bin/.
I am including some screenshots in case it helps / show what has already been tried (sorry for the sizes being all over the place).
You might want to reinstall Abcpdf, from Nuget or reinstall the correct version on the server depending on how it's set up.
ABCGecko cannot function without the XULRunner38_0 folder in the same directory as ABCGeckoWP.exe.
On x64 Windows, even if ABCGeckoWP.exe is found only in %SystemRoot%\System32 (though it should be placed only in %SystemRoot%\SysWOW64 for being 32-bit), it never looks up XULRunner38_0 folder in %SystemRoot%\System32 (but in %SystemRoot%\SysWOW64) because of File System Redirection.
So maybe check the file location as stated above.
This error looks like the version of ABCPdf that you are using and the version installed on the server are not the same.
I would also recommend upgrading the version to the latest one and using the Chrome render engine.
I have a package which includes a file that gets frequently rebuilt. This causes meteor to restart each time that file is edited.
There are ways to get meteor to ignore files within the main app, eg putting inside a .directory but is there a way to do this within a package?
The catch is that I DO need the final file to be included for deployment, so it has to be named - as an asset - and included in the package addFiles.
The only solution I have so far is to host the asset external to the meteor app and load it in via http or something on each cold start, but that's a bit fragile.
As of Meteor v1.5.2.1, there is support for a .meteorignore file. It behaves the same as a .gitignore. Have you tried using it?
You can use them in any directory of your project and are fully integrated with the file watching system.
I've used plugins before, but after I recompiled my qt libraries, I haven't been able to successfully use .svg image files any longer. There error I get is as follows:
file:///C:/Users/RBhatia/Documents/SettingsMenu/SettingsMenu/SlicingComp.qml:41:5: QML Image:
Error decoding:
file:///C:/Users/RBhatia/Documents/SettingsMenu/SettingsMenu/img/sliceStep_slice1.svg: Unsupported image format
I have checked all my .dll files to make sure they are in 64 bit format. I also checked my environment variables, and even tried to use different librariesm but I simply cannot figure out what changed to cause this issue.
The problem is not missing header files. It's due to missing dependencies to Qt libraries as mentioned in that comment here: Comment by JamesL
To use SVG images you need to specify QtSvg, QtXml, QtGui, and QtCore to be deployed with your project.
The most probable reason I can think of is that you were missing some svg header files when you compiled your qt. If you do not add -svg to your configure, svg is treated as optional. Means if everything is there to build the svg plugin, it is build, else this feature is silently dropped.
You said, you checked your .dll files. Did you also check the plugins folder? Something like $QTDIR/plugins/imageformats. Must contains a qsvg4.dll. Or qsvg5.dll for Qt5.
Upgraded to the latest 0.6.0 of meteor and Collection API is not define, meteor does not start correctly any more:
ReferenceError: CollectionAPI is not defined
I copy pasted collectionapi to app "packages" folder, but still does not run. Is there anything else I have to do, to use Collection API with latest meteor 0.6.0?
meteor add collectionapi - says: collectionapi: already using
Thanks in advance for any kind of information and help!
I'm not sure copying and pasting packages is a good idea. Have you tried reinstalling it with meteor remove collectionapi and then adding it again?
Update: I seem to be getting the same problem with one of my packages, chartjs. It's now giving a similar error to yours, saying ReferenceError: Chart is not defined. Previously Chart was scoped to the window, so it could be accessed in my client JS files. It must be due to the scoping changes in 0.6.0, but I'm not sure yet how to resolve it - probably the package itself needs updating.
Update 2: Yup, akshat was dead right, the JS file at the heart of the chartjs package needed the var Chart changing to just Chart so it would be scoped to the window object. Have sent a pull request to the package.
Yes, thanks for answers. Fix is also available for download in CollectionAPI github:
https://github.com/crazytoad/meteor-collectionapi/pull/12
I have imported an existing project into flex but any changes I make to the source are not being built and displayed when I test run the application. The original files which are in the bin-debug folder dont seem to be changing at all.
I have tried cleaning the project, deleting the bin-debug folder even reinstalling flex builder, but nothing has solved the problem.
I've read this post which was about the same problem but none of the advice helped.
Any advice would be appreciated.
When you imported the project did you do a default import (copies everything into your workspace) or an "Existing Projects into Workspace" import?
If you did the default (listed as "FlexBuilder/Flex Project" under the import source) then you might be changing the wrong code. If you're looking in the original project's location for the SWFs to run then you're in the wrong place, as the SWFs you build will be in the new location.
One quick way to test to see if your code is actually being compiled would be to intentionally put a compile error in there. If the compiler chokes on it then your code is being compiled.
There's another thing you can try. I just ran into a weird issue where FB was caching a compile error, and even after fixing the file it still showed the error. Even after doing a clean, restarting FB, etc.
I found a place where FB caches information for the project, and for some reason it wasn't clearing things it should. It's possible your project's cache got messed up and it's messing up the compile somehow. You can try deleting it (might need to delete and re-import your project though).
The cache is at:
workspace.metadata.plugins\org.eclipse.core.resources.projects\
I just made a blog post about this, in case you'd find it useful.