Jump to content

Can't access Logs


ravedog

Recommended Posts

Posted (edited)

Hello,

 

I cannot access anything that involves getting to a file. For instance: when I want to log at the log (Tools > Log...) it immediately opens up a Finder save window (well, Java's poor implementation of the Finder window) and it's path is defaulting to deep inside the Java plug in Directory....) you cannot navigate anywhere else on the hard drive... when you go to the drives root and click on Users... it shows nothing in the directory. Even i pick an external drive and click save nothing happens. Someone on another post suggested that try to change the view options to get things to show up (which ironically works when trying to save a backup file or navigating to a new firmware file, but not here... anything in the File menu (save backups etc... works)...

 

So I have no ability to do anything that requires looking at the log file. Which is a problem...

 

I know this is a Mac Java issue but seriously, this product should not be allowed to be used by Mac users if it is not on par with other OS's. It's super frustrating. Just updating firmware or saving a backup is extremely cumbersome and unreliable.

 

Why can't a user look at logs within the app?

 

BTW - flushing cache or updating Java is not a solution. And I'm on 4.2.8 on GUI and Firmware... that's not the issue either.

 

On a side note, sorry if I sound bitchy but I have to tell you the whole java experience on the Mac with ISY has made me almost want to sell everything and consider something else (home automation... Not the Mac).

Edited by ravedog
Posted

Hello,

 

I cannot access anything that involves getting to a file. For instance: when I want to log at the log (Tools > Log...) it immediately opens up a Finder save window (well, Java's poor implementation of the Finder window) and it's path is defaulting to deep inside the Java plug in Directory....) you cannot navigate anywhere else on the hard drive... when you go to the drives root and click on Users... it shows nothing in the directory. Even i pick an external drive and click save nothing happens. Someone on another post suggested that try to change the view options to get things to show up (which ironically works when trying to save a backup file or navigating to a new firmware file, but not here... anything in the File menu (save backups etc... works)...

 

So I have no ability to do anything that requires looking at the log file. Which is a problem...

 

I know this is a Mac Java issue but seriously, this product should not be allowed to be used by Mac users if it is not on par with other OS's. It's super frustrating. Just updating firmware or saving a backup is extremely cumbersome and unreliable.

 

Why can't a user look at logs within the app?

 

BTW - flushing cache or updating Java is not a solution. And I'm on 4.2.8 on GUI and Firmware... that's not the issue either.

 

On a side note, sorry if I sound bitchy but I have to tell you the whole java experience on the Mac with ISY has made me almost want to sell everything and consider something else (home automation... Not the Mac).

 

I believe you and the majority feel the same way about Java.  :mrgreen:  Enduring never ending updates, clearing the cache, seeing java socket errors, blah blah, really is pain.

 

I can't wait until this system moves away from the whole java platform . . .

Posted

Honestly I can't see how. Unless they can manage a pure web experience. If they drop java then it might become OS specific.

 

Besides. The fact that one part of the app can access files (backup restore) and the other can't (logs) makes me think it's bad programming. I don't know if the devs even have a Mac but getting a mini for testing at least would be prudent. Because it's not acceptable to being able to access key features. And judging by the few Mac related posts this issue is nothing new.

Posted

Honestly I can't see how. Unless they can manage a pure web experience. If they drop java then it might become OS specific.

 

Besides. The fact that one part of the app can access files (backup restore) and the other can't (logs) makes me think it's bad programming. I don't know if the devs even have a Mac but getting a mini for testing at least would be prudent. Because it's not acceptable to being able to access key features. And judging by the few Mac related posts this issue is nothing new.

 

From other related posts it was suggested the system might move to a HTML5 sort of deployment structure. I am just guessing at this point in time, so take that with a hefty grain of salt!

 

Also, off the top of my head a lot of the restrictions you noted are a Mac related issue. Apple has been loathed to support Java from the on set.

Posted

From other related posts it was suggested the system might move to a HTML5 sort of deployment structure. I am just guessing at this point in time, so take that with a hefty grain of salt!

 

Also, off the top of my head a lot of the restrictions you noted are a Mac related issue. Apple has been loathed to support Java from the on set.

 

It's not apple java anymore - hasn't been for a while. It's now provided directly by oracle. And yeah I was guessing this is a Mac thing judging how there are no complaints by the majority of windows people here. I do hope it's a web front end solution that may come, although they are fairly tight-lipped at future plans.

Posted

Hi ravedog,

 

You are 100% justified in feeling frustrated. This must be resolved and as soon as possible.

 

Can you please make sure your backup/restore always works? This is odd since they use the same exact object (Util.FileUtils).

 

I am so very sorry.

 

With kind regards,
Michel

Posted

Hi Michel.

 

Yes. I can get it to work but it's a pain. The backup dialog will come up with usually the root for my user account. It shows the folders. Double click a folder. Shows nothing. Switch view from list view to 3 pane then it shows contents of that folder. Double click in the next folder. Again nothing. Switch views back. Shows next level. Have to toggle back n forth until I reach the destination. Then I can save.

 

This also the same procedure for firmware. It works but laborious.

 

The logging stuff starts off with a default directory buried way in the system folder. And it never works.

Posted

I will try yo get on that next 24 hours. Thank you!

Guest
This topic is now closed to further replies.

×
×
  • Create New...