gvlekke / gpsassist-update Goto Github PK

What steps will reproduce the problem?

Insert memory card in slot on iMac, nothing now happens - no growler 
notification 

What is the expected output? What do you see instead?

Expect grower update message

What version of the product are you using? On what operating system?

Latest, running on Lion

Please provide any additional information below.

There is the slight chance this was caused by the move to a new iMac as they 
both happened at the same time.

Would be useful to have a manual override in these cases.

What steps will reproduce the problem?
1. Just state that the program has finished it's task and that all data has 
been stored
2.
3.

What is the expected output? What do you see instead?
More clear for 1st time users that the program has completed it's task.

What version of the product are you using? On what operating system?
v1.0

Please provide any additional information below.
Great tool! Tnx, Arthur

What steps will reproduce the problem?
1. Select something from the menu  (About) 
2. If another application is currently active, the dialog will be behind that 
application.

What is the expected output? What do you see instead?
Dialog should be on foreground

Would be fine to have the Growl 1.3 Framework included. 

I have changed the framework folder inside your app manually - that works.

greetings
michael franz

What steps will reproduce the problem?
1. For some reason it won't update anymore and the gpsassist date has now 
expired. stuck on 19-3 2011 - 17-4 -2011.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?
1.0.1 

Please provide any additional information below.
Just wondering if this is or has happened to anyone else?
email - [email protected]

What steps will reproduce the problem?
1. regular update with mac is not working at all
2.
3.

What is the expected output? What do you see instead?
nothing

What version of the product are you using? On what operating system?
mac 10.6.6.

Please provide any additional information below.

What steps will reproduce the problem?
1. insert 64GB card
2. no requester appears


What is the expected output? What do you see instead?
Growl requester prompting to register card

What version of the product are you using? On what operating system?
v1.0.1 on Mac OS 10.7.4

Please provide any additional information below.
gpsassist-update works fine for my low capacity cards but refuses to "see" my 
new 64GB SDXC card formatted with ExFAT. To check what's the problem I 
formatted it with FAT32 but it's still not recognized. My older cards (2GB SD 
with FAT and 16GB or 32GB SDHC with FAT32) work just fine. I assume there is 
some kind of limit built in gpsassist-update which prevents cards >32GB to be 
recognized.

What steps will reproduce the problem?
1. Start GPS-Assist

What is the expected output? What do you see instead?
No HDD-Access of GPSAssist at all or atleast only when SD-Card inserted.

What version of the product are you using? On what operating system?
1.0.1, Lion 10.7 and SnowLion 10.8

Please provide any additional information below.
I have observed high HDD activity on my iMac (SSD + HDD) for weeks. Finally I 
closed App after App finding that quitting GPSAssist will quite down the HDD. 
This is reproducible.

What steps will reproduce the problem?
1. Insert an SD card that has been registered for updates

What is the expected output? What do you see instead?
Expected to see a growl notification that the update was successful.  Growl 
notifications indicate that the volume is correctly identified, but the update 
fails and the gps assist data is not updated in the SD card

Here are the growl notifications:
GPSAssist Update - GPSAssist detected disk
NO NAME

"GPSAssist-data update failed for disk NO NAME"


What version of the product are you using? On what operating system?
gpsassist-update 1.0.1; macosx 10.7.3

Please provide any additional information below.
running the original gpsassist script in a terminal window works fine

This seems to have started with the upgrade to 10.7.3