I am working with adobe air-app. I created a background worker. and in that worker if I create a new local shared object or want to get attach to my local shared object. It creates a new shared object but I am unable to get its physical location.
I suggest you have a look on stackoverflow or google about it. Since you do not required something else special I hope the following links can help
how to validate the radio button group? in flex
http://captaincode.wordpress.com/2009/10/29/validating-a-checkbox-in-flex-via-mxml/
Related
I want to create custom alert action on Splunk that will ingest saved searches from splunk to my software. I have gone through the documentation:
https://docs.splunk.com/Documentation/Splunk/latest/AdvancedDev/ModAlertsIntro
My issue is I want some guidelines in creating this custom alert action. I have gone through a youtube video: https://www.youtube.com/watch?v=UqJAc7rpFmQ .He created the UI using code. Do I need to code as well? If yes, do I create folders on my local desktop and then how to integrate the code on splunk for testing? And which folder will pass the saved search to my source code?
Or can I use add-on builder to create this?
So far, I have created an add-on using an add-on builder and declared input parameters and edited the script but it doesnot seem to work.
I just need some guidance to kick start my project.
Any help would be highly appreciated.
Here is the image of the asset information widget, which can add a property called c8y_Address
I would like my device to show their address information on the asset information widget, but I don't really know how to upload these properties to a device.
I am using MQTT. So I created a customised SMQRT Template, which is a POST inventory method 001,<region>,<street>,<territory>. And then I publish it using client.publish('s/uc/TemplateName',001,${region},${address},${territory});. But it doesn't work.
I'm just wondering how can we use API to add the address information as a property of a device?
Thank you.
POST would create a new object. I guess what you want to do is updating the device with this properties. So a PUT template would be the correct choice.
Note that the preview shown in the UI currently is incorrect for PUT templates.
It says:
999,<c8y_Address.region>,<c8y_Address.street>,<c8y_Address.territory>
but it actually needs to be (like described in the SmartREST 2.0 guide):
999,<externalId>,<c8y_Address.region>,<c8y_Address.street>,<c8y_Address.territory>
The externalId needs to be from the device you want to update (if you only have a single device without children it would be what you also use as MQTT clientId).
I'm trying to create live tiles in my app by using BitmapRender (in Windows 8.1) to create an image from a user control, which I then want to add as my live tile image.
Creating the image works perfectly, and I store it in the app's roaming folder. However, I can't get the image to add to the live tile when created this way. The odd thing is that if I copy my generated file into the project and then try to attach it to the live tile it works (so the image must be correctly formatted/size, etc.); and if I copy a random image into my roaming folder and set that as the live tile image it also works (meaning I am able to use a file in the roaming folder to set the tile image)...so that means I am referencing the file location correctly, and the image itself is capable of being used on a live tile...so why doesn't it work?
I have created a sample project (link below) that illustrates that my live tile creating code works (with an image stored in the project), and also that I can successfully create an image from a UI control and store it in the roaming folder (FWIW I've tried using different folders with no change in behaviour).
Is there something I'm missing? Any insight or help would be greatly appreciated.
Project is in VB.net, but I can figure out answers in C# if that's easier.
Sample project to illustrate the issue
The trouble is that you're attempting to use an absolute file path to reference the image, which is not supported. If you look in the tile schema, specifically at the page for the element, you'll see that the src must be an URI using http[s]://, ms-appx:///, or ms-appdata:///local for Windows Store apps. The fact that you can use a relative in-package path of /livetile.png is a bit of a fluke, as that's defaulting to ms-appx:///livetile.png.
What you need to do, then, is just use this for a filepath:
filepath = "ms-appdata:///local/livetile.png"
I tried this in your sample and it worked fine. Do note that only the local folder is supported here, not roaming. This is primarily because roaming appdata is limited to 100K to begin with, and dropping tile images in there would often quickly fill your quota. You'll want to then generate the image locally on each device (which would make sense also because you can then take the current scaling into account).
Since it's possible to download Game Center metadata through Transporter into a .itmsp package file, how would you edit and upload that file using Application Loader? I see no interface for Game Center metadata in Application Loader. Application Loader is default app to open .itmsp packages. Did I miss something?
At worst best I guess it could be possible to edit the contained .xml file, add a few achievements, and then try to upload that into iTunes Connect using Application Loader.
If you make a lookup on an existing app inside your Itunes account, you download a file called like like the vendor_id with the .itmsp format. My experience was, opening this file by double clicking inside the Application Loaderjust changes the data inside this archive.
In my case, an additional file was created called something like meta-local... and the metadata.xml from Itunes Connect has been changed. It's like the Application Loader deletes information like description, keywords, url`s, screenshots and all the data you have to define the first time you create the app before uploading the binary.
Instead of using the Application Loader you should open the .itmsp file by right clicking and selecting show package content. This way nothing will be changed and you can open the metadata and change specific data.
I don't have Game Center elements included in my app yet but I did some researches on tools which could automate the process of generating and changing data. Have a look at these projects, the first one looks like it could be exactly what you're looking for:
iTunes Transporter Generator
iTunes Store Connector
iTunes Store Transporter Web
If not maybe you could create an Apple Script to parse the metadata.xml and add or change your data.
I would appreciate if you could leave a comment if any of these tools could help you with the Game Center problem.
I want to add login items programmatically in Mountain Lion (10.8).
Until now I was able to add login items by editing this plist:
/Users/test/Library/Preferences/loginwindow.plist
and adding items (path,name,hide) to AutoLaunchedApplicationDictionary dictionary
in the OS doesn't work anymore. Items that are added to this dictionary are not launched on login. I see that the login items are saved in a file called: com.apple.loginitems.plist
but I don't understand how to add an item to this file. I tried to add the item to CustomListItems dictionary with parameters like name,path, hide but they were not launched on login.
Does anyone know how can I add from code login item?
I understand you want to start your program automatically when your user logs in.
In older versions of OS X, it was possible to add login items manually by editing loginwindow.plist. Apple deprecated this approach when they added LaunchAgent and LaunchDaemon functionality to the OS.
Since you are using Mountain Lion, the correct way to have a program launch is to create a launchagent for it. This is a .plist file that you can use to tell OS X to a) perform some action (e.g.: launch /some/program.app) when b) a specific event occurs (e.g.: logging in, logging out, etc)
You will find Apple's official document on creation of LaunchAgents over here.
This looks like a great tutorial on the modern way of doing things: The launch at login sandbox project
It starts with a paragraph buried in the App Sandbox design guide:
Creating a Login Item for Your App
To create a login item for your sandboxed app, use the SMLoginItemSetEnabled function (declared in ServiceManagement/SMLoginItem.h) as described in “Adding Login Items Using the Service Management Framework” in Daemons and Services Programming Guide.
(With App Sandbox, you cannot create a login item using functions in the LSSharedFileList.h header file. For example, you cannot use the function LSSharedFileListInsertItemURL. Nor can you manipulate the state of launch services, such as by using the function LSRegisterURL.)
And rolls from there...