Existing users, 
 plist Class for REALbasic - 2.11.1stores your app's preferences |
|
||||||||||||||
|
|||||||||||||||
Feedback Summary:
| This Version: | |||||
| Overall Rating: | Not rated (0.0) | Features: | Not rated (0.0) | Support: | Not rated (0.0) |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | Not rated (0.0) | Price: | Not rated (0.0) |
Key to Types of Feedback:
Reviews 
Troubleshooting 
Usage Tips 
Developer Notes 
Commentary 
Featured Reviews
All Feedback: 1 - 10 of 10
Fixed version available - Version: 2.11.1, 1/4/2010 05:07PM PST
(1 of 1 users found this comment useful)
MarkusWinter
Two more problems - Version: 2.11.1, 7/11/2008 10:51AM PST
MarkusWinter
(1) Don't use GetReal & SetReal - they are suppossed to replace GetDouble & SetDouble but they don't work (haven't had time to locate the error yet)
(2) As soon as I add the plist (but not plist dict) to my app the app looses it's menubar in the IDE. Even when you set the menu bar again, save it and load it - then the app menubar is gone again
(2) As soon as I add the plist (but not plist dict) to my app the app looses it's menubar in the IDE. Even when you set the menu bar again, save it and load it - then the app menubar is gone again
Bug repair - Version: 2.11.1, 11/12/2007 05:48AM PST
MarkusWinter
Doh.
Replacement should have been
values.value(key) = Format(v, "-#.#################")
Replacement should have been
values.value(key) = Format(v, "-#.#################")
Easiest way to make proper preference files in REALbasic 
- Version: 2.11.1, 11/3/2007 03:17AM PST
MarkusWinter
Takes out a lot of hassle, and is versatile and stable.
Developer seems no longer reachable under the address given at the website but as you get the complete source code you can fix any bugs yourself.
Developer seems no longer reachable under the address given at the website but as you get the complete source code you can fix any bugs yourself.
Same bug in SetReal - Version: 2.11.1, 11/2/2007 07:45AM PST
MarkusWinter
The same bug is in SetReal
Replace
values.value(key)=Str(v)
with
values.value(key)=Format(v, "############")
End Sub
Replace
values.value(key)=Str(v)
with
values.value(key)=Format(v, "############")
End Sub
Possible bug in SetDouble - Version: 2.11.1, 11/1/2007 06:58AM PST
MarkusWinter
Hi,
nice work on the plist class but I think I found a bug:
when I write
dim d as new date
EditField1.text = str(d.TotalSeconds)
I always get it in scientific notation as 3.276756e+9 because that’s how strings handle doubles
When I save d.Totalseconds with
prefs.root.SetDouble("TotalSeconds", TotalSeconds)
it becomes 3276756000.000000 which is wrong
However I noticed that the code in the plist class is
Sub SetDouble(key As string,v As double)
dim result As integer
dim value As string
result=CheckType(key,"real")
if result<>0 then
values.value(key)=str(v)
types.value(key)="real"
searched.Value(key)=false
end
End Sub
I think this line
values.value(key)=str(v)
is responsible and possibly a bug in plist. It should be replaced with
values.value(key)=Format(v, "############")
Best Regards
Markus
nice work on the plist class but I think I found a bug:
when I write
dim d as new date
EditField1.text = str(d.TotalSeconds)
I always get it in scientific notation as 3.276756e+9 because that’s how strings handle doubles
When I save d.Totalseconds with
prefs.root.SetDouble("TotalSeconds", TotalSeconds)
it becomes 3276756000.000000 which is wrong
However I noticed that the code in the plist class is
Sub SetDouble(key As string,v As double)
dim result As integer
dim value As string
result=CheckType(key,"real")
if result<>0 then
values.value(key)=str(v)
types.value(key)="real"
searched.Value(key)=false
end
End Sub
I think this line
values.value(key)=str(v)
is responsible and possibly a bug in plist. It should be replaced with
values.value(key)=Format(v, "############")
Best Regards
Markus
Possible bug in SetDouble - Version: 2.11.1, 11/1/2007 06:55AM PST
MarkusWinter
Hi,
nice work on the plist class but I think I found a bug:
when I write
dim d as new date
EditField1.text = str(d.TotalSeconds)
I always get it in scientific notation as 3.276756e+9 because that’s how strings handle doubles
When I save d.Totalseconds with
prefs.root.SetDouble("TotalSeconds", TotalSeconds)
it becomes 3276756000.000000 which is wrong
However I noticed that the code in the plist class is
Sub SetDouble(key As string,v As double)
dim result As integer
dim value As string
result=CheckType(key,"real")
if result<>0 then
values.value(key)=str(v)
types.value(key)="real"
searched.Value(key)=false
end
End Sub
I think this line
values.value(key)=str(v)
is responsible and possibly a bug in plist. It should be replaced with
values.value(key)=Format(v, "############")
Best Regards
Markus
nice work on the plist class but I think I found a bug:
when I write
dim d as new date
EditField1.text = str(d.TotalSeconds)
I always get it in scientific notation as 3.276756e+9 because that’s how strings handle doubles
When I save d.Totalseconds with
prefs.root.SetDouble("TotalSeconds", TotalSeconds)
it becomes 3276756000.000000 which is wrong
However I noticed that the code in the plist class is
Sub SetDouble(key As string,v As double)
dim result As integer
dim value As string
result=CheckType(key,"real")
if result<>0 then
values.value(key)=str(v)
types.value(key)="real"
searched.Value(key)=false
end
End Sub
I think this line
values.value(key)=str(v)
is responsible and possibly a bug in plist. It should be replaced with
values.value(key)=Format(v, "############")
Best Regards
Markus
Great Stuff - Version: 2.0, 8/25/2005 11:22AM PST
(2 of 2 users found this comment useful)
smard
Thanx to the developer.
You can download the fixed plist here:
http://dl.dropbox.com/u/992591/REALbasic/Classes/plist%202010-01-04.zip
and an introduction on how to use it here
http://www.declaresub.com/wiki/index.php/Property_lists_and_how_to_make_them_using_the_plist_class
Enjoy.