problem when sorting by address in the last release

[James Sentman]

I have often thought that we needed a sort of sub log of more important things. I’m not sure just stopping the log scrolling is really the best way to do that because it could have applications beyond just letting you see it for a little longer.  I have considered making the log file live reload things after your changing of the toolbar to show alerts or everything so that you can switch back and forth. Maybe add a count there of the different log lines in the different categories that are available. I have considered doing a sort of alert system that is a separate list that could open and have more info added to it. I haven’t decided just what to do yet. 

There are a couple of ways you can display more info as an alert that don’t interrupt XTension that you might consider. In 10.9 and forward  you can do a system notification from applescript that will show up on the desktop and then disappear after the normal timeout period while still staying in the notifications list. Thats very simple just:


display notification “something interesting has happened”

the entire dictionary entry has a few other things you can use like title, subtitle and play a system sound:

display notification v : Display a notification. At least one of the body text and the title must be specified.
display notification [text] : the body text of the notification
[ with title (text) ] : the title of the notification (default is the name of the calling application).
[ subtitle (text) ] : the subtitle of the notification
[ sound name (text) ] : the name of the sound to play


You can also tell the system events background app to display an alert while ignoring application responses so that XTension doesn’t wait for the response. That works well and will leave the dialog up until you dismiss it. You can also add a “giving up after 30” to have it close the window automatically for you after some amount of time if you’re not there. But there is a bug in there if I recall correctly and multiple dialogs open at the same time, only the most recent one will actually timeout. So if you open a second dialog while a first one is still there, the giving up after time will get lost for one or the other of them and leave them up. This is no problem really, but you should avoid creating thousands of those or your system may start to run out of memory for more windows.


ignoring application responses
  tell app “System Events”
    display alert “something interesting has happened!” giving up after 10
  end tell
end ignoring

I want to ultimately do an alert system that will popup in any place that you’re actually looking at the data, on your phone or on the webpage. I need to get around to doing a native iPhone app before I can send alerts directly to that platform without the app actually running and sending web page notifications requires servers as well in the cloud so I think I’ll just do a separate sort of notification system in the web app that will popup as fading alerts on the page you’re looking at while providing a way to show previous ones or something… I haven’t decided how that will work exactly yet.

> On Sep 24, 2016, at 9:45 PM, Rob Lewis <rob at whidbey.com> wrote:
> 
> P.S. Curious if you have any response to my “freeze log” feature idea of a few days ago. 
> 

Thanks,
 James


James Sentman                       http://www.PlanetaryGear.org		http://MacHomeAutomation.com




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.machomeautomation.com/pipermail/xtensionlist/attachments/20160925/f34ef7e4/attachment.html>