Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for 'real' keys & values #86

Closed
apizz opened this issue Nov 28, 2018 · 2 comments
Closed

Add support for 'real' keys & values #86

apizz opened this issue Nov 28, 2018 · 2 comments

Comments

@apizz
Copy link
Collaborator

apizz commented Nov 28, 2018

In both of the manifests I've been working on - AirServer & DetectX Swift - both use real number keys (<real></real>) in some capacity.

However, it appears that when real numbers are used as part of a preference in a manifest, the preference doesn't appear at all. Here is an example:

                  <dict>
			<key>pfm_name</key>
			<string>SUScheduledCheckInterval</string>
			<key>pfm_type</key>
			<string>real</string>
			<key>pfm_description</key>
			<string>Frequency to complete automatic software update checks.</string>
			<key>pfm_range_list</key>
			<array>
				<real>3600</real>
				<real>86400</real>
				<real>604800</real>
				<real>2629800</real>
			</array>
			<key>pfm_range_list_titles</key>
			<array>
				<string>Hourly</string>
				<string>Daily</string>
				<string>Weekly</string>
				<string>Monthly</string>
			</array>
		</dict>
@erikberglund
Copy link
Collaborator

That is currently only set when using float, but good idea, is should add real as an alias too.

@erikberglund
Copy link
Collaborator

I've added this to the next update. You can then use both real or float for the floating point numbers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants