Smalltalk › Instantiations

Hover Help Manager: syncExecInUI: for currentPointerLocation missing

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Noschvie

Hover Help Manager: syncExecInUI: for currentPointerLocation missing

AbtEwHoverHelpManager>>#backgroundProcess

there are two calls of "self currentPointerLocation", the second call is running under UI but the first call doesn't.

For the first call of "self currentPointerLocation" the syncExecInUI: shall be added like this:

    CwAppContext default syncExecInUI: [
        currPointerLocation := self currentPointerLocation.
    ].

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/va-smalltalk.
For more options, visit https://groups.google.com/d/optout.

Seth Berman

Re: Hover Help Manager: syncExecInUI: for currentPointerLocation missing

Thank you much Norbert,

I agree with your change.

Created Case 63955: Hover Help Manager: syncExecInUI: for currentPointerLocation missing
to fix this.

- Seth

On Monday, August 20, 2018 at 4:08:48 AM UTC-4, Norbert Schlemmer wrote:

AbtEwHoverHelpManager>>#backgroundProcess

there are two calls of "self currentPointerLocation", the second call is running under UI but the first call doesn't.

For the first call of "self currentPointerLocation" the syncExecInUI: shall be added like this:

    CwAppContext default syncExecInUI: [
        currPointerLocation := self currentPointerLocation.
    ].

Noschvie

Re: Hover Help Manager: syncExecInUI: for currentPointerLocation missing

Thanks!

Am Mittwoch, 22. August 2018 20:26:53 UTC+2 schrieb Seth Berman:

Thank you much Norbert,

I agree with your change.
Created Case 63955: Hover Help Manager: syncExecInUI: for currentPointerLocation missing
to fix this.

- Seth

On Monday, August 20, 2018 at 4:08:48 AM UTC-4, Norbert Schlemmer wrote:
AbtEwHoverHelpManager>>#backgroundProcess

there are two calls of "self currentPointerLocation", the second call is running under UI but the first call doesn't.

For the first call of "self currentPointerLocation" the syncExecInUI: shall be added like this:

    CwAppContext default syncExecInUI: [
        currPointerLocation := self currentPointerLocation.
    ].