leaflet-draw
"name": "leaflet-draw",
"description": "Vector drawing plugin for Leaflet",
"version": "1.0.2",
leaflet-snap
"name": "leaflet-snap",
"version": "0.0.3",
"description": "Enable snapping between layers",
leaflet-draw-toolbar
"version": "0.3.0-alpha.1"
When run with this configuration snap editing is not working - i mean the points to which it's supposed to snap are not showing up and "sticking" not happens. But if i add the leaflet-draw dependency from the same package as a leaflet-snap (L.drawVersion = '0.3.0-dev';
) then sticking is working fine, but i lose the ability to edit features, as when the dragging points are shown but moving them doesn't change the position of them. So i think there is a version compatibility issue and I tried a lot of version combinations to make everything work, without success. In my opinion Leaflet.Snap requires some older version of Leaflet.Draw while leaflet-draw-toolbar requires a higher one.
Related
I am trying to create a Electron app and use rollup to live preview my app. package.json:
"scripts": {
"build": "rollup -c",
"dev": "rollup -c -w",
},
However, every time I change something and the app gets updated, the focus switches away from VS Code and I have to go back to it using the mouse or Alt-Tab, which is of course very cumbersome.
Is there something I can do to prevent this focus change from happening? I have set the autosave timer to 10s for now, but I really would prefer to avoid this issue altogether.
Thank you in advance!
Edit: I remembered that I have an older version of VS Code on my laptop, so I copied the settings from there to my desktop and it solved the issue. I have no idea which is/was the offending setting, but I'm sure glad the issue is solved.
Of course, it would be interesting for other readers who have the same problem what the problematic setting was.
I have been watching tutorials on youtube (i'm new to unity), I was trying to add a rigid body to my player, which I've never done. In the video they clicked add component in the inspector then physics then rigid body. but i don't see physics and when I search for it nothing appears. the only options i get are:
Effects
Layout
Mesh
Miscellaneous
Rendering
New Script
Underneath Box Collider i get a warning saying the the "module that implements this component type has been force excluded in player settings" could this be the problem? If so how would i fix it?
Thanks.
Try go to the PackageManager, switch to Built-In Packages and see if the package Physics is installed. Sounds like it has been actively be removed (uninstalled) or you somehow broke the Packages/manifest.json file.
If you can't even get the PackageManager try to reset the packages as described here via the top menu bar → Help → Reset Packages to defaults
or just directly replace your Packages/manifest.json with a one from a fresh empty project
Also note
Our first TECH stream release of the year is available as of today. Unity 2020.1 includes a wide range of features and improvements that make Unity workflows even more intuitive and make you more productive, while Unity 2019 LTS remains the recommended version for projects in production.
The PackageManager got an overhaul and a lot of users had issues like yours. See e.g. this thrread.
You should stick to the LTS versions, currently 2019.4 LTS (except for experimenting with the very newest features).
So if you type in the search bar of Add Component "Rigid" nothing pops up? If not I believe it should.
The problem could be in your libraries. Try deleting the library in your project (with Unity closed). Maybe if you have not made much progress in this project you could try opening a new unity project and seeing if it works.
The Unity documentation clearly shows Tile Palette available under Window > 2D.
But I don't have the option available:
Where can I access the Tile Palette menu?
I'm on OSX 10.13.6 and Unity version 2019.2.1f1
#AJP I was just having a similar issue using 2019.2 Personal.
I found that I needed to add the tile map package to the project, then "Tile Palette" appeared as an option under "Window".
To do this:
Go to Window > Package Manager.
Click 2d Tilemap Editor on the left of the pop up.
Then click install in the lower right hand corner (Install will be replaced with "Remove" once installed).
2dTileMapPackage
Update 2020/08/03
The issue is fixed in Unity 2019.3 and beyond, where the tile palette option shows up as expected on iOS, making it likely the issue was caused by a bug in 2019.2
As per AJP's own findings: Tile Palette is not available on Mac OSX. But if it was this would be a work around for any menu not showing up in the toolbar.
(I could only test this on windows, but I assume this works on a mac aswel, under the same locations.)
Under Edit there is the option "shortcuts". Go into this window and search for "Tile pallete". Click the Tile palette command and set your custom shortcut. You should now be able to open it without it showing up under the Window > 2D tab.
If it doesn't show up there either then my only guess would be that it isn't installed in your current Unity version (which appears to be the case on mac OSX)
If you're like me and no solution is working please READ THIS!
The problem is with Unity Hub and not Unity as a whole. I discovered this late late last night when I was reinstalling for the 5th time.
On my 5th install and reboot, I opened "Unity" instead of "Unity Hub" and sure enough there it was. I closed "Unity" and opened "Unity Hub" and sure enough when I booted into "Unity" it was gone. There is something wrong with the back end loading it would seem when loading from Unity Hub.
For a problem that seems to have plagued people for years. I'm shocked Unity developers haven't come across this solution and patched it.
You will have to install the according package like RobC and Jere already mentioned..
It's the same if you miss Sprite Editor.
You just have to install the according package which in your case is 2D Tilemap Editor
Window > Package Manager search for the according package,
in this case 2D Tilemap Editor.
If you miss the Sprite Editor the package to install is:
-"2D Sprite", I guess
I updated BW6 studio from 6.2.1 to 6.2.2 and when I reloaded a project, I ran into this issue. I'm not able to visually see the elements. I can see the elements in the outline view, which then outlines their location on the screen, as the screenshot shows.
Things I tired(and didn't work) :
Highlighting them all, and dragging them down.
Same as above, but using the keyboard keys and down arrowing them
Restore from TFS, even the older versions do the same thing.
I can't seem to get my addon icon to show up when I use jpm. The relevant items in package.json are
"icon": "icon.png",
"icon64": "icon64.png",
and when I unpack the extension, I see them in install.rdf as
<em:iconURL>icon.png</em:iconURL>
<em:icon64URL>icon64.png</em:icon64URL>
They are 48x48 and 64x64px png files, respectively.
Both of those files are in the root directory of the extension. If I read the docs correctly, I shouldn't even have to specify those names, as they are the default.
I don't see any extension icon in the Addons-manager. What am I doing wrong?
This is a known issue with jpm, and I just updated that bug report asking for an update on what we can do about it. It's a mystery to me why it doesn't work as-is.
it's a bug.
If you're working on jpm 1.0.1, the only way it works is:
"icon": "resource://#youraddonname/icon.png",
rename your icon as "icon". Don't know why it works that way..
For new jpm tool, you can use like this:
"icon :" "resource://<ADDONID>/data/icon.png"
Note: In cfx you have id that is some things like jid1-O1iNqbs7ifwqvA but in new jpm tool , we dont have any id, instead the name field use instead of #jetpack...
for example for an old cfx addon with id of jid1-O1iNqbs7ifwqvA we must do like this
"id": "jid1-O1iNqbs7ifwqvA#jetpack",
"icon": "resource://jid1-O1iNqbs7ifwqvA-at-jetpack/data/icon.png"
also you can add icons for menu bar, addon page, open menu Menu like below:
"icons":{
"16":"./data/icon-16.png",
"32":"./data/icon-32.png",
"64":"./data/icon-64.png",
"128":"./data/icon-128.png",
"256":"./data/icon-256.png",
"512":"./data/icon-512.png"
},
useful Links:
Learn Make Package.json
file
JPM Manual