Is there a simple way to set an application's icon using canoncial-quickly? I have tried setting the icon file of the main window within Glade, but the application still uses one of the stock GTK icons as its main icon in Unity on Ubuntu 12.04 LTS.
Navigate to the directory with your Quickly Ubuntu application in it. Let's say it's called myproj. Inside myproj is a directory named data. Inside data is a directory named media. And in there you should see a graphic file named myproj.svg. Replace myproj.svg with a scalable vector graphics image of your choice. You can either download an svg off the web, or create one for yourself in Inkscape. The next time you run your application, it will pick up myproj.svg as its icon.
Related
I am trying to edit existing project in unity version 2017.1.3f1 my goal is to change the value of a text script using direct edit from the inspector. However everytime i save the project and run the application the change i have made is not reflecting. Can any one advice me on how to deal with this.
The methods that i have tried
Click the gear icon to load the csharp script but always showing error code
"Unable to open C:/Program Files/Unity/Editor/Data/UnityExtensions/Unity/GUISystem/Standalone/UnityEngine.UI.dll: Check external application preferences.
I have change editor from MONO and Visual Studio but still no luck.
i have attached here some images that can help understand my concern.
RED circle is for the text wanted to change and the gear icon is suppose to leas the code but showing error as mention above
You are using Unity, and therefore the component system. The text is part of the old (deprecated) set of GUI components.
The editor window only allows you to cache the text that will be displayed. In order to load/change text, you need to create a C# script. C# script is added by pressing the AddComponent button, for example. Next, you need to use the Using UnityEngine.UI directive for your component, or TMPro for the Text Mesh Pro component.
If your changes don't show up, it's likely that the project has a system that loads certain texts into your text field. In this case, you need to find out which script is responsible for this.
I am trying out Rundeck using the open source docker image (rundeck:3.3.8). I can add a custom logo after the default Rundeck logo, but I cannot replace the default Rundeck logo with my own. Is that even possible? I have tried searching the png file of the Rundeck logo but cannot find that as well in my Ubuntu system?
Additionally, is it possible to change the display size of the custom logo? As you can see from the following snapshot, it enlarges my custom logo quite a bit from its original size.
That logo isn't replaceable, you can add a logo besides that one, take look at this. The file isn't located on the operating system, is located inside the WAR (java executable) file (at /home/rundeck path). The best way to change that logo is to get the Rundeck code, make your changes, and build your own version following this.
I am working with CMake 2.8.10.2 on Mac OS X 10.7.5.
I've configured CMake to build a simple application with Xcode that creates an empty window. I then tried to configure CMake to build a DMG installation of the program specifying a background image using:
set(CPACK_DMG_BACKGROUND_IMAGE /path/to/image)
and custom .DS_Store to set windows size and icon placement using:
set(CPACK_DMG_DS_STORE /path/to/DS_Store file)
Xcode will successfully build the application and create the disk image. When I mount the image it comes up with the correct size and icon placement, however the background is always set to white instead of specified background image.
What is needed to get the background to display properly in the disk image?
Unfortunately no one has responded this question. This has been a frustrating experience, however, it looks like I finally solved it so I'm posting a description here to save someone else the grief if they ever have to deal with this.
In order for a background to work on an installation image, basically two things must happen; the background file must exist within the installation image, and the .DS_Store at the root of the image must be configured to use that background.
The .DS_Store file can be configured by mounting the install image in a writable state and then selecting Show View Options from the Finder's View menu. From there someone will select the Picture option for the Background and drag the background file to the placeholder in the Show View Options panel.
When working with CPack, the trick is to be able to drag the image. When someone sets the background for the installation, builds, and mounts the image it will not look like there is any background to drag to the Show View Options panel. If someone goes into the Terminal and does
ls -a
on the root of the mounted install, that command will list, among other things, a file called background.png. This file does not display in the Finder.
The reason this file displays in the Terminal and not the Finder is because it has an extended attributes that makes it hidden for the Finder. Since the file is hidden from the Finder it is not possible to drag the file to the Show View Options panel. Doing
ls -l#
will reveal what extended attributes are applied to the file. There should be only one called com.apple.FinderInfo. Removing this attribute should make the file visible in the Finder. The attribute can be removed using this command from the Terminal
xattr -d com.apple.FinderInfo background.png
After removing the attribute the background file still will not show up in the Finder right away. Someone will have to eject and remount the install image. Once this has happened, the background file should appear in the Finder and someone can drag it to the Show View Options panel, which will cause the background image to display in the Finder window for the install image. After that, someone can copy the .DS_Store file from the root of the install image and apply it to the CPACK_DMG_DS_STORE attribute, and the background image should appear whenever an install image is built.
#TronThomas response helped me out dramatically. Not to supplant his answer, here's some additional information about the process that I just worked through. For reference, this is with MacOS Sierra and CMake 3.6.2.
Set a background image with set(CPACK_DMG_BACKGROUND_IMAGE /path/to/image)
Create the DMG file using the CPack generator DragNDrop
Mount the image in read/write mode using a shadow file hdiutil attach mypackage.dmg -shadow junk.dmg
At this point, we don't see a background image, but one exists in the folder .background in the DMG file. Our strategy will be to use Finder to make the window exactly how we want, then copy out the .DS_Store file.
On the Finder menu, click View->Show View Options
Under Background:, click the Picture radio button. Then, click the image above the text Drag Image Here. Note, the current view must be as Icons otherwise this dialog will not be there.
In the file dialog, go back to the mounted DMG image. Then, press cmd-shift-. This should show the hidden folders. From here, go into the .background folder and select the background image.
If everything has worked properly, the background image should now be visible.
Adjust the windows size and view or hide toolbars as desired on the View menu. The exact settings will be replicated by the installer.
Copy off the the hidden .DS_Store file in the root directory of the volume to another location. The cmd-shift-. trick can be used view the file or just use the Terminal at this point to copy everything. Note, we can change the name of this file to DS_Store, so that it's not hidden when we store it.
Eject the DMG file from Finder. Delete junk.dmg or any shadow files remaining.
Back in the CMakeLists.txt, set the variable set(CPACK_DMG_DS_STORE /path/to/DS_Store) This is the file that we just created and moved off of the volume.
Rebuild the DMG file with CPack. Everything should be as viewed before.
As a warning, there's a lot of information that gets stored in the .DS_Store file such as file locations, user names, and the like. At the moment, I don't know how to control this information, so be a little careful when distributing the final DMG file. If you're curious as to what's in there, use a hex editor like xxd.
As a brief comment, this process is very obtuse. That said, I don't think it's Kitware's fault. Though, they could document the process better. From what I can tell, the .DS_Store file format is not well documented or disclosed, so we're basically forced to use Finder to make one for us. This is a MacOS issue that probably should be fixed.
I have some Unity .asset files which contains 3D models. I want to be able to convert / export these 3D models into a more common format which will be accepted by 3D Max.
I read that I need to use a custom script since Unity doesn't support this out of the box, so I tried to set up this plugin script:
http://wiki.unity3d.com/index.php?title=ObjExporter
I created a new project called Test, copied the two CS scripts into the "My Project Name/Editor" folder, and although the custom tab in Unity shows up, it is not click-able.
Also, I had to change line 79 to:
objMaterial.textureName = AssetDatabase.GetAssetPath(mats[material].mainTexture);
From:
objMaterial.textureName = EditorUtility.GetAssetPath(mats[material].mainTexture);
As it was giving me an error.
Which version of Unity? In 3.5.7 you should see the following:
The Custom menu item should be in the main tool bar. Also included for reference is the project hierarchy, to show that the scripts are in the correct folder. I copied the scripts verbatim from the OP's link.
When building an Eclipse RCP application you get to define the window images in the .product and plugin.xml files for the application plugin. These are the images that show up in the upper-left corner of the main application window. But say you want to use this same image in a dialog window that your application might open. How do you get access to this image programmatically?
In my use case I am building two products that only differ in branding elements so I wanted all my dialogs to be consistent and use the same branding image that the main application window uses.
I figured out the answer through some trial and error and failed web searches. Turns out it is as simple as:
shell.setImage(ApplicationWindow.getDefaultImage());
(for completeness, I'm currently developing in Eclipse 3.8. Not sure if this carries forward to Juno/4.X)