[interfacekit] Re: BDeskbar weirdness

>> Yes, it's pretty strange and does not really make sense.
>> I have checked the Deskbar sources and it does nothing about this, 
>> so, in the 
>> original implementation, it's the BDeskbar class which performs the 
>> (useless) 
>> check and also makes a copy of the name.
>
>Mmh, maybe it's a typo of the BDeskbar implementor and should be 
>`found_name != NULL'. Anyway, there are a lot of bugs/weirdnesses in 
>the API, so don't worry. ;-) For the Storage Kit we record the R5 
>oddities we encounter and comment problems with our implementation in 
>docs/develop/storage/Annotations. Maybe it's a good idea to do that 
for 
>the other kits as well.

So, I plan to not have any check of what *found_name is (either NULL or 
non-NULL).  I will comment that code with details of how it deviates 
from Be's implementation and why that implementation is not what we 
want.

On a sad note, my Intel box seems to have died.  I think it is the 
power supply so hopefully I can get it fixed and up and running soon.  
My only other box is a BeBox so I can't really do alot more development 
until it is fixed.  So BDeskbar will wait a short time until I 
resurrect my machine.  Luckily, I have checked in all but a couple of 
files which weren't working right and needed re-writing anyways so if I 
lose the HD, nothing is lost from an openbeos perspective (I will be 
very upset though).

>CU, Ingo

--
Jeremy Rand
jrand@xxxxxxxx

Other related posts: