O$ Studio 5.2.3.x and OSX 10.12.6 — anybody having issues in development mode
Getting to reproduce easily is not easy, along with the frequent BOOM when saving files as binaries to FrontBase in v8.0, some thing that has been easy to do in v5 for years.
So a few teething pains currently. Hmmmm…
Mike
Mike Matthews, Managing Director, Lineal Software Solutions Ltd
Apple Reseller, Microsoft Partner, SQLWorks Business Partner
phone: 01271 375999 | web: lineal.co.uk <www.lineal.co.uk/> | email: mike.matthews@lineal.co.uk <mailto:mike.matthews@lineal.co.uk>
> On 25 Aug 2017, at 16:23, Doug Easterbrook <doug@artsman.com> wrote:
>
> hi Mike.
>
> I don’t yet have our application fully migrated to studio 8 on OSX .. is on the list to do soon. so I can’t tell you if we see the same (yet).
>
> but I would let omnis support know if you have a reproducible case..
>
> We have a timer proc running in the background for logoff purposes — it fires every minute or so — but I don’t see an abnormal drain in Studio 5.
>
> hmmm. something to watch for
>
> Doug Easterbrook
> Arts Management Systems Ltd.
> mailto:doug@artsman.com
> www.artsman.com
> Phone (403) 650-1978
>
>> On Aug 25, 2017, at 8:14 AM, Mike Matthews <omnis@lineal.co.uk> wrote:
>>
>> Doug,
>>
>> Interesting point. I have noticed on OSX 10.12.6 with v8.8.3.2 & v8.1.0.0, there is a massive CPU hog somewhere, but looking at other 10.12.x Macs here, it is not isolated to 10.12.6 really.
>>
>> Activity monitor shows between 75% & 95% usage when moving the mouse around a window. This was not so with v5.x or v6.x either.
>>
>> On the Runtime v8.03, the drain is not as large. But when watching the CPU activity, just moving the mouse around the TopWin, no clicks, just moving it, 80+% of CPU is taken by Omnis.
>>
>> Open Activity monitor and try it with any version of V8 and let me know what you get. We do have a timer object running all of the time however.
>>
>> Mike
>>
>>
>>
>> Mike Matthews, Managing Director, Lineal Software Solutions Ltd
>>
>> Apple Reseller, Microsoft Partner, SQLWorks Business Partner
>> phone: 01271 375999 | web: lineal.co.uk <www.lineal.co.uk/> | email: mike.matthews@lineal.co.uk <mailto:mike.matthews@lineal.co.uk>
>>> On 25 Aug 2017, at 14:56, Doug Easterbrook <doug@artsman.com> wrote:
>>>
>>> hi Andy.
>>>
>>> the other thought I have is …. timer procedures under 10.12.6 — I’m finding that they are quirky with this release of the OS
>>>
>>> sometimes, a direct application of a timer procedure will not fire — even if told to do so.
>>>
>>> and the other thing we do is postgres sql calls in the background thread — which I know uses timer procedures as part of its implementation to get the data to the method that is to received i when the background thread is complete.
>>>
>>>
>>> are you using a lot of those???
>>>
>>>
>>>
>>>
>>>
>>> Doug Easterbrook
>>> Arts Management Systems Ltd.
>>> mailto:doug@artsman.com
>>> www.artsman.com
>>> Phone (403) 650-1978
>>>
>>>> On Aug 25, 2017, at 6:52 AM, Andy Hilton <andyh@totallybrilliant.com> wrote:
>>>>
>>>> Yes the OS seems to be the determining factor on my users side as well…..
>>>>
>>>>
>>>>> On Aug 25, 2017, at 8:21 AM, Doug Easterbrook <doug@artsman.com> wrote:
>>>>>
>>>>> hi Andy:
>>>>>
>>>>> All of our team have retina displays — but I’m the only one with the ribbon bar above the keyboard.
>>>>>
>>>>> I’ll watch for what I find — I have seen slowishness at time redrawing menus, but I have not see and transactions get rolled back (we use postgres) after quit.
>>>>>
>>>>>
>>>>> good to hear that I”m not the only one — It’ll take time to figure the issue — I’m currently blaming OSX 10.12.6 since all was fie before that.
>>>>>
>>>>>
_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com
