set-frame-parameter a child-frame's 'parent-frame error on macOS ?

classic Classic list List threaded Threaded
48 messages Options
123
Reply | Threaded
Open this post in threaded view
|

set-frame-parameter a child-frame's 'parent-frame error on macOS ?

tumashu
The test code:
----------------
(let ((test (let ((after-make-frame-functions nil))
              (make-frame
               `((parent-frame . ,(window-frame))
                 (width . 10)
                 (height . 10))))))
  (set-frame-parameter test 'parent-frame (window-frame)))
----------

The error:
-------
Debugger entered--Lisp error: (error "Invalid specification of ‘parent-frame’")
  modify-frame-parameters(#<frame Emacs 0x114d8b960> ((parent-frame . #<frame *scratch* 0x106815a30>)))
  set-frame-parameter(#<frame Emacs 0x114d8b960> parent-frame #<frame *scratch* 0x106815a30>)
  (let ((test (let ((after-make-frame-functions nil)) (make-frame (cons (cons 'parent-frame (window-frame)) '((width . 10) (height . 10))))))) (set-frame-parameter test 'parent-frame (window-frame)))
  eval((let ((test (let ((after-make-frame-functions nil)) (make-frame (cons (cons 'parent-frame (window-frame)) '((width . 10) (height . 10))))))) (set-frame-parameter test 'parent-frame (window-frame))) nil)
  elisp--eval-last-sexp(nil)
  #f(compiled-function (eval-last-sexp-arg-internal) "Evaluate sexp before point; print value in the echo area.\nInteractively, with a non `-' prefix argument, print output into\ncurrent buffer.\n\nNormally, this function truncates long output according to the\nvalue of the variables `eval-expression-print-length' and\n`eval-expression-print-level'.  With a prefix argument of zero,\nhowever, there is no such truncation.  Such a prefix argument\nalso causes integers to be printed in several additional formats\n(octal, hexadecimal, and character when the prefix argument is\n-1 or the integer is `eval-expression-print-maximum-character' or\nless).\n\nIf `eval-expression-debug-on-error' is non-nil, which is the default,\nthis command arranges for all errors to enter the debugger." (interactive "P") #<bytecode 0x400d4227>)(nil)
  #f(compiled-function (&rest _it) #<bytecode 0x413d1275>)()
  eval-sexp-fu-flash-doit-simple(#f(compiled-function (&rest _it) #<bytecode 0x413d1275>) #f(compiled-function (&rest args2) #<bytecode 0x45362dbd>) #f(compiled-function (&rest args2) #<bytecode 0x45362ddd>))
  eval-sexp-fu-flash-doit(#f(compiled-function (&rest _it) #<bytecode 0x413d1275>) #f(compiled-function (&rest args2) #<bytecode 0x45362dbd>) #f(compiled-function (&rest args2) #<bytecode 0x45362ddd>))
  esf-flash-doit(#f(compiled-function (&rest _it) #<bytecode 0x413d1275>) #f(compiled-function (&rest args2) #<bytecode 0x45362dbd>) #f(compiled-function (&rest args2) #<bytecode 0x45362ddd>) #f(compiled-function (&rest args2) #<bytecode 0x45362dfd>))
  ad-Advice-eval-last-sexp(#f(compiled-function (eval-last-sexp-arg-internal) "Evaluate sexp before point; print value in the echo area.\nInteractively, with a non `-' prefix argument, print output into\ncurrent buffer.\n\nNormally, this function truncates long output according to the\nvalue of the variables `eval-expression-print-length' and\n`eval-expression-print-level'.  With a prefix argument of zero,\nhowever, there is no such truncation.  Such a prefix argument\nalso causes integers to be printed in several additional formats\n(octal, hexadecimal, and character when the prefix argument is\n-1 or the integer is `eval-expression-print-maximum-character' or\nless).\n\nIf `eval-expression-debug-on-error' is non-nil, which is the default,\nthis command arranges for all errors to enter the debugger." (interactive "P") #<bytecode 0x400d4227>) nil)
  apply(ad-Advice-eval-last-sexp #f(compiled-function (eval-last-sexp-arg-internal) "Evaluate sexp before point; print value in the echo area.\nInteractively, with a non `-' prefix argument, print output into\ncurrent buffer.\n\nNormally, this function truncates long output according to the\nvalue of the variables `eval-expression-print-length' and\n`eval-expression-print-level'.  With a prefix argument of zero,\nhowever, there is no such truncation.  Such a prefix argument\nalso causes integers to be printed in several additional formats\n(octal, hexadecimal, and character when the prefix argument is\n-1 or the integer is `eval-expression-print-maximum-character' or\nless).\n\nIf `eval-expression-debug-on-error' is non-nil, which is the default,\nthis command arranges for all errors to enter the debugger." (interactive "P") #<bytecode 0x400d4227>) nil)
  eval-last-sexp(nil)
  eros-eval-last-sexp(nil)
  funcall-interactively(eros-eval-last-sexp nil)
  call-interactively(eros-eval-last-sexp nil nil)
  command-execute(eros-eval-last-sexp)
-------
Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

martin rudalics
 > The test code:
 >
 > ----------------
 > (let ((test (let ((after-make-frame-functions nil))
 >                (make-frame
 >                 `((parent-frame . ,(window-frame))
 >                   (width . 10)
 >                   (height . 10))))))
 >    (set-frame-parameter test 'parent-frame (window-frame)))
 > ----------

I'm not sure what this code is supposed to do.  First you make a new
child frame named 'test' with the selected frame as its parent.  Then
you want to set the parent frame of 'test' to the selected frame.

But I'm afraid that the implementation of x_set_parent_frame in
nsterm.m has a bug which I didn't notice before.  It uses FRAME_X_P
although it probably should use FRAME_NS_P.  And this

 > Debugger entered--Lisp error: (error "Invalid specification of ‘parent-frame’")
 >    modify-frame-parameters(#<frame Emacs 0x114d8b960> ((parent-frame . #<frame *scratch* 0x106815a30>)))
 >    set-frame-parameter(#<frame Emacs 0x114d8b960> parent-frame #<frame *scratch* 0x106815a30>)
 >    (let ((test (let ((after-make-frame-functions nil)) (make-frame (cons (cons 'parent-frame (window-frame)) '((width . 10) (height . 10))))))) (set-frame-parameter test 'parent-frame (window-frame)))
 >    eval((let ((test (let ((after-make-frame-functions nil)) (make-frame (cons (cons 'parent-frame (window-frame)) '((width . 10) (height . 10))))))) (set-frame-parameter test 'parent-frame (window-frame))) nil)
 >    elisp--eval-last-sexp(nil)
 >    #f(compiled-function (eval-last-sexp-arg-internal) "Evaluate sexp before point; print value in the echo area.\nInteractively, with a non `-' prefix argument, print output into\ncurrent buffer.\n\nNormally, this function truncates long output according to the\nvalue of the variables `eval-expression-print-length' and\n`eval-expression-print-level'.  With a prefix argument of zero,\nhowever, there is no such truncation.  Such a prefix argument\nalso causes integers to be printed in several additional formats\n(octal, hexadecimal, and character when the prefix argument is\n-1 or the integer is `eval-expression-print-maximum-character' or\nless).\n\nIf `eval-expression-debug-on-error' is non-nil, which is the default,\nthis command arranges for all errors to enter the debugger." (interactive "P") #<bytecode 0x400d4227>)(nil)
 >    #f(compiled-function (&rest _it) #<bytecode 0x413d1275>)()
 >    eval-sexp-fu-flash-doit-simple(#f(compiled-function (&rest _it) #<bytecode 0x413d1275>) #f(compiled-function (&rest args2) #<bytecode 0x45362dbd>) #f(compiled-function (&rest args2) #<bytecode 0x45362ddd>))
 >    eval-sexp-fu-flash-doit(#f(compiled-function (&rest _it) #<bytecode 0x413d1275>) #f(compiled-function (&rest args2) #<bytecode 0x45362dbd>) #f(compiled-function (&rest args2) #<bytecode 0x45362ddd>))
 >    esf-flash-doit(#f(compiled-function (&rest _it) #<bytecode 0x413d1275>) #f(compiled-function (&rest args2) #<bytecode 0x45362dbd>) #f(compiled-function (&rest args2) #<bytecode 0x45362ddd>) #f(compiled-function (&rest args2) #<bytecode 0x45362dfd>))
 >    ad-Advice-eval-last-sexp(#f(compiled-function (eval-last-sexp-arg-internal) "Evaluate sexp before point; print value in the echo area.\nInteractively, with a non `-' prefix argument, print output into\ncurrent buffer.\n\nNormally, this function truncates long output according to the\nvalue of the variables `eval-expression-print-length' and\n`eval-expression-print-level'.  With a prefix argument of zero,\nhowever, there is no such truncation.  Such a prefix argument\nalso causes integers to be printed in several additional formats\n(octal, hexadecimal, and character when the prefix argument is\n-1 or the integer is `eval-expression-print-maximum-character' or\nless).\n\nIf `eval-expression-debug-on-error' is non-nil, which is the default,\nthis command arranges for all errors to enter the debugger." (interactive "P") #<bytecode 0x400d4227>) nil)
 >    apply(ad-Advice-eval-last-sexp #f(compiled-function (eval-last-sexp-arg-internal) "Evaluate sexp before point; print value in the echo area.\nInteractively, with a non `-' prefix argument, print output into\ncurrent buffer.\n\nNormally, this function truncates long output according to the\nvalue of the variables `eval-expression-print-length' and\n`eval-expression-print-level'.  With a prefix argument of zero,\nhowever, there is no such truncation.  Such a prefix argument\nalso causes integers to be printed in several additional formats\n(octal, hexadecimal, and character when the prefix argument is\n-1 or the integer is `eval-expression-print-maximum-character' or\nless).\n\nIf `eval-expression-debug-on-error' is non-nil, which is the default,\nthis command arranges for all errors to enter the debugger." (interactive "P") #<bytecode 0x400d4227>) nil)
 >    eval-last-sexp(nil)
 >    eros-eval-last-sexp(nil)
 >    funcall-interactively(eros-eval-last-sexp nil)
 >    call-interactively(eros-eval-last-sexp nil nil)
 >    command-execute(eros-eval-last-sexp)

looks very similar to Bug#30019's

Debugger entered--Lisp error: (error "Invalid specification of ‘parent-frame’")
   modify-frame-parameters(#<frame Emacs 0x11571e7d0> ((parent-frame .
#<frame *Warnings* 0x10982e5b0>)))
   set-frame-parameter(#<frame Emacs 0x11571e7d0> parent-frame #<frame
*Warnings* 0x10982e5b0>)

Alan, please have a look.

Thanks, martin


Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

tumashu
martin rudalics <[hidden email]> writes:

>> The test code:
>>
>> ----------------
>> (let ((test (let ((after-make-frame-functions nil))
>>                (make-frame
>>                 `((parent-frame . ,(window-frame))
>>                   (width . 10)
>>                   (height . 10))))))
>>    (set-frame-parameter test 'parent-frame (window-frame)))
>> ----------
>
> I'm not sure what this code is supposed to do.  First you make a new
> child frame named 'test' with the selected frame as its parent.  Then
> you want to set the parent frame of 'test' to the selected frame.
>

The above just a example to show bug.

I want to use child-frame as popup menu of company.
so I want reuse exist child-frame instead of recreate a new one.
for the speed.

when I switch to other frame, child-frame's parent-frame must be reseted.



> But I'm afraid that the implementation of x_set_parent_frame in
> nsterm.m has a bug which I didn't notice before.  It uses FRAME_X_P
> although it probably should use FRAME_NS_P.  And this
>
>> Debugger entered--Lisp error: (error "Invalid specification of ‘parent-frame’")
>>    modify-frame-parameters(#<frame Emacs 0x114d8b960> ((parent-frame . #<frame *scratch* 0x106815a30>)))
>>    set-frame-parameter(#<frame Emacs 0x114d8b960> parent-frame #<frame *scratch* 0x106815a30>)
>>    (let ((test (let ((after-make-frame-functions nil)) (make-frame
>> (cons (cons 'parent-frame (window-frame)) '((width . 10) (height
>> . 10))))))) (set-frame-parameter test 'parent-frame (window-frame)))
>>    eval((let ((test (let ((after-make-frame-functions nil))
>> (make-frame (cons (cons 'parent-frame (window-frame)) '((width . 10)
>> (height . 10))))))) (set-frame-parameter test 'parent-frame
>> (window-frame))) nil)
>>    elisp--eval-last-sexp(nil)
>>    #f(compiled-function (eval-last-sexp-arg-internal) "Evaluate sexp
>> before point; print value in the echo area.\nInteractively, with a
>> non `-' prefix argument, print output into\ncurrent
>> buffer.\n\nNormally, this function truncates long output according
>> to the\nvalue of the variables `eval-expression-print-length'
>> and\n`eval-expression-print-level'.  With a prefix argument of
>> zero,\nhowever, there is no such truncation.  Such a prefix
>> argument\nalso causes integers to be printed in several additional
>> formats\n(octal, hexadecimal, and character when the prefix argument
>> is\n-1 or the integer is `eval-expression-print-maximum-character'
>> or\nless).\n\nIf `eval-expression-debug-on-error' is non-nil, which
>> is the default,\nthis command arranges for all errors to enter the
>> debugger." (interactive "P") #<bytecode 0x400d4227>)(nil)
>>    #f(compiled-function (&rest _it) #<bytecode 0x413d1275>)()
>>    eval-sexp-fu-flash-doit-simple(#f(compiled-function (&rest _it)
>> #<bytecode 0x413d1275>) #f(compiled-function (&rest args2)
>> #<bytecode 0x45362dbd>) #f(compiled-function (&rest args2)
>> #<bytecode 0x45362ddd>))
>>    eval-sexp-fu-flash-doit(#f(compiled-function (&rest _it)
>> #<bytecode 0x413d1275>) #f(compiled-function (&rest args2)
>> #<bytecode 0x45362dbd>) #f(compiled-function (&rest args2)
>> #<bytecode 0x45362ddd>))
>>    esf-flash-doit(#f(compiled-function (&rest _it) #<bytecode
>> 0x413d1275>) #f(compiled-function (&rest args2) #<bytecode
>> 0x45362dbd>) #f(compiled-function (&rest args2) #<bytecode
>> 0x45362ddd>) #f(compiled-function (&rest args2) #<bytecode
>> 0x45362dfd>))
>>    ad-Advice-eval-last-sexp(#f(compiled-function
>> (eval-last-sexp-arg-internal) "Evaluate sexp before point; print
>> value in the echo area.\nInteractively, with a non `-' prefix
>> argument, print output into\ncurrent buffer.\n\nNormally, this
>> function truncates long output according to the\nvalue of the
>> variables `eval-expression-print-length'
>> and\n`eval-expression-print-level'.  With a prefix argument of
>> zero,\nhowever, there is no such truncation.  Such a prefix
>> argument\nalso causes integers to be printed in several additional
>> formats\n(octal, hexadecimal, and character when the prefix argument
>> is\n-1 or the integer is `eval-expression-print-maximum-character'
>> or\nless).\n\nIf `eval-expression-debug-on-error' is non-nil, which
>> is the default,\nthis command arranges for all errors to enter the
>> debugger." (interactive "P") #<bytecode 0x400d4227>) nil)
>>    apply(ad-Advice-eval-last-sexp #f(compiled-function
>> (eval-last-sexp-arg-internal) "Evaluate sexp before point; print
>> value in the echo area.\nInteractively, with a non `-' prefix
>> argument, print output into\ncurrent buffer.\n\nNormally, this
>> function truncates long output according to the\nvalue of the
>> variables `eval-expression-print-length'
>> and\n`eval-expression-print-level'.  With a prefix argument of
>> zero,\nhowever, there is no such truncation.  Such a prefix
>> argument\nalso causes integers to be printed in several additional
>> formats\n(octal, hexadecimal, and character when the prefix argument
>> is\n-1 or the integer is `eval-expression-print-maximum-character'
>> or\nless).\n\nIf `eval-expression-debug-on-error' is non-nil, which
>> is the default,\nthis command arranges for all errors to enter the
>> debugger." (interactive "P") #<bytecode 0x400d4227>) nil)
>>    eval-last-sexp(nil)
>>    eros-eval-last-sexp(nil)
>>    funcall-interactively(eros-eval-last-sexp nil)
>>    call-interactively(eros-eval-last-sexp nil nil)
>>    command-execute(eros-eval-last-sexp)
>
> looks very similar to Bug#30019's
>
> Debugger entered--Lisp error: (error "Invalid specification of ‘parent-frame’")
>   modify-frame-parameters(#<frame Emacs 0x11571e7d0> ((parent-frame .
> #<frame *Warnings* 0x10982e5b0>)))
>   set-frame-parameter(#<frame Emacs 0x11571e7d0> parent-frame #<frame
> *Warnings* 0x10982e5b0>)
>
> Alan, please have a look.
>
> Thanks, martin
>

--


Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

martin rudalics
 >>> (let ((test (let ((after-make-frame-functions nil))
 >>>                 (make-frame
 >>>                  `((parent-frame . ,(window-frame))
 >>>                    (width . 10)
 >>>                    (height . 10))))))
 >>>     (set-frame-parameter test 'parent-frame (window-frame)))
 >>> ----------
 >>
 >> I'm not sure what this code is supposed to do.  First you make a new
 >> child frame named 'test' with the selected frame as its parent.  Then
 >> you want to set the parent frame of 'test' to the selected frame.
 >>
 >
 > The above just a example to show bug.

OK.  But setting the parent frame two times for the same frame makes
it difficult to say which instance causes the bug.  Anyway, can you
try the trivial patch to nsterm.m below?

Thanks, martin


diff --git a/src/nsterm.m b/src/nsterm.m
index 5798f4f..1a6066f 100644
--- a/src/nsterm.m
+++ b/src/nsterm.m
@@ -1932,7 +1932,7 @@ so some key presses (TAB) are swallowed by the system. */
    if (!NILP (new_value)
        && (!FRAMEP (new_value)
   || !FRAME_LIVE_P (p = XFRAME (new_value))
-  || !FRAME_X_P (p)))
+  || !FRAME_NS_P (p)))
      {
        store_frame_param (f, Qparent_frame, old_value);
        error ("Invalid specification of `parent-frame'");


Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

Alan Third
On Fri, Jan 12, 2018 at 07:47:53PM +0100, martin rudalics wrote:

> >>> (let ((test (let ((after-make-frame-functions nil))
> >>>                 (make-frame
> >>>                  `((parent-frame . ,(window-frame))
> >>>                    (width . 10)
> >>>                    (height . 10))))))
> >>>     (set-frame-parameter test 'parent-frame (window-frame)))
> >>> ----------
> >>
> >> I'm not sure what this code is supposed to do.  First you make a new
> >> child frame named 'test' with the selected frame as its parent.  Then
> >> you want to set the parent frame of 'test' to the selected frame.
> >>
> >
> > The above just a example to show bug.
>
> OK.  But setting the parent frame two times for the same frame makes
> it difficult to say which instance causes the bug.  Anyway, can you
> try the trivial patch to nsterm.m below?

The patch gets rid of the error message for me. Perhaps it will also
fix bug#30019.
--
Alan Third

Reply | Threaded
Open this post in threaded view
|

Re:Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

tumashu
In reply to this post by martin rudalics
Seem to fix the problem, thanks,  https://github.com/tumashu/company-childframe/issues/3#issuecomment-357404832



At 2018-01-13 02:47:53, "martin rudalics" <[hidden email]> wrote: > >>> (let ((test (let ((after-make-frame-functions nil)) > >>> (make-frame > >>> `((parent-frame . ,(window-frame)) > >>> (width . 10) > >>> (height . 10)))))) > >>> (set-frame-parameter test 'parent-frame (window-frame))) > >>> ---------- > >> > >> I'm not sure what this code is supposed to do. First you make a new > >> child frame named 'test' with the selected frame as its parent. Then > >> you want to set the parent frame of 'test' to the selected frame. > >> > > > > The above just a example to show bug. > >OK. But setting the parent frame two times for the same frame makes >it difficult to say which instance causes the bug. Anyway, can you >try the trivial patch to nsterm.m below? > >Thanks, martin > > >diff --git a/src/nsterm.m b/src/nsterm.m >index 5798f4f..1a6066f 100644 >--- a/src/nsterm.m >+++ b/src/nsterm.m >@@ -1932,7 +1932,7 @@ so some key presses (TAB) are swallowed by the system. */ > if (!NILP (new_value) > && (!FRAMEP (new_value) > || !FRAME_LIVE_P (p = XFRAME (new_value)) >- || !FRAME_X_P (p))) >+ || !FRAME_NS_P (p))) > { > store_frame_param (f, Qparent_frame, old_value); > error ("Invalid specification of `parent-frame'"); >
Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

martin rudalics
In reply to this post by Alan Third
 > The patch gets rid of the error message for me. Perhaps it will also
 > fix bug#30019.

Thanks for checking.

martin

Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

martin rudalics
In reply to this post by tumashu
 > Seem to fix the problem, thanks,  https://github.com/tumashu/company-childframe/issues/3#issuecomment-357404832

Checked in on the release branch.  Thanks for the test case.

martin

Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

tumashu
martin rudalics <[hidden email]> writes:

>> Seem to fix the problem, thanks,  https://github.com/tumashu/company-childframe/issues/3#issuecomment-357404832
>
> Checked in on the release branch.  Thanks for the test case.
>
> martin
>

Thanks!

by the way, for this issue: https://github.com/tumashu/company-childframe/issues/2

I have tested many times, but can not find the reason.

Do you suggest where I should first find?

1. Child-frame
2. HiDPI
3. Window manager
4. Other

--


Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

martin rudalics
 > by the way, for this issue: https://github.com/tumashu/company-childframe/issues/2
 >
 > I have tested many times, but can not find the reason.
 >
 > Do you suggest where I should first find?
 >
 > 1. Child-frame
 > 2. HiDPI
 > 3. Window manager
 > 4. Other

I don't understand the issue and not even whether it occurs with MacOS
or Unity.  Can you tell me more?

martin

Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

Dmitry Gutov
On 1/13/18 2:58 PM, martin rudalics wrote:

> I don't understand the issue and not even whether it occurs with MacOS
> or Unity.  Can you tell me more?

Unity, Ubuntu 17.04.

Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

martin rudalics
 > Unity, Ubuntu 17.04.

And what is the issue?  That link

https://send.firefox.com/download/793d8dab0f/#ziyoHhB0usYUs4mBCp5Q0w

"has expired or never existed in the first place!"

martin

Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

tumashu
In reply to this post by martin rudalics
martin rudalics <[hidden email]> writes:

>> by the way, for this issue: https://github.com/tumashu/company-childframe/issues/2>
>> I have tested many times, but can not find the reason.
>>
>> Do you suggest where I should first find?
>>
>> 1. Child-frame
>> 2. HiDPI
>> 3. Window manager
>> 4. Other
>
> I don't understand the issue and not even whether it occurs with MacOS
> or Unity.  Can you tell me more?

It's not my machine's issue, it is like this:

when I want to show company-child-frame-menu at <position>, I support
this position is (20, 50), but before show menu about 0.1s, this menu will be showed
at positon (10, 25), and dispear and then show at position (20, 50),
this is so fast, let menu look flicker.

>
> martin
>

--


Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

tumashu
In reply to this post by martin rudalics
martin rudalics <[hidden email]> writes:

>> by the way, for this issue: https://github.com/tumashu/company-childframe/issues/2>
>> I have tested many times, but can not find the reason.
>>
>> Do you suggest where I should first find?
>>
>> 1. Child-frame
>> 2. HiDPI
>> 3. Window manager
>> 4. Other
>
> I don't understand the issue and not even whether it occurs with MacOS
> or Unity.  Can you tell me more?

Dmitry Gutov's machine seem to active HiDPI feature


> martin
>

--


Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

Dmitry Gutov
In reply to this post by martin rudalics
On 1/13/18 3:29 PM, martin rudalics wrote:
>  > Unity, Ubuntu 17.04.
>
> And what is the issue?  That link
>
> https://send.firefox.com/download/793d8dab0f/#ziyoHhB0usYUs4mBCp5Q0w
>
> "has expired or never existed in the first place!"

Here's that video: https://youtu.be/wU044PoC4pA?t=30

Guess that's the place I'm going to publish screencasts to from now on. :)

Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

martin rudalics
In reply to this post by tumashu
 > when I want to show company-child-frame-menu at <position>, I support
 > this position is (20, 50), but before show menu about 0.1s, this menu will be showed
 > at positon (10, 25), and dispear and then show at position (20, 50),
 > this is so fast, let menu look flicker.

Does that happen with Robert Pluim's `set-frame-position' scaling
patch?

martin

Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

martin rudalics
In reply to this post by Dmitry Gutov
 > Here's that video: https://youtu.be/wU044PoC4pA?t=30
 >
 > Guess that's the place I'm going to publish screencasts to from now on. :)

Sorry.  Neither VLC nor Firefox are capable here to show that video
satisfactorily.  After playing it three times I was able to see the
menu once for a short moment only.

martin

Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

Dmitry Gutov
On 1/14/18 12:05 PM, martin rudalics wrote:

> Sorry.  Neither VLC nor Firefox are capable here to show that video
> satisfactorily.

Really? I'm using Firefox, on GNU/Linux. And it plays back fine. I can
send it to you personally (the original mkv) if you like.

> After playing it three times I was able to see the
> menu once for a short moment only.

Yeah, weird. I open it 3 times there.

Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

Dmitry Gutov
In reply to this post by martin rudalics
On 1/14/18 12:05 PM, martin rudalics wrote:

> Does that happen with Robert Pluim's `set-frame-position' scaling
> patch?

Yes. Without it, both positions were far from point.

Reply | Threaded
Open this post in threaded view
|

Re: set-frame-parameter a child-frame's 'parent-frame error on macOS ?

martin rudalics
In reply to this post by Dmitry Gutov
> Really? I'm using Firefox, on GNU/Linux. And it plays back fine. I can send it to you personally (the original mkv) if you like.

Please send me the mkv.

Thanks, martin


123