From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: test request for octave
Date: Thu, 27 Dec 2018 14:39:00 -0000 [thread overview]
Message-ID: <c5108e82-3cf5-371c-e6b2-6a3e03b9cec5@gmail.com> (raw)
In-Reply-To: <9682ac18-02aa-d97e-28a3-1f0507e35523@maxrnd.com>
Am 27.12.2018 um 09:59 schrieb Mark Geisert:
> Marco Atzeri wrote:
>> Hi,
>> I am trying to understand if octave has a problem
>> with Cygwin X interface or it is a specific
>> issue on my new Laptop
>>
>> Can someone make this test from octave
>> in a Xterm ?
>>
>> Â available_graphics_toolkits()
>> Â graphics_toolkit("fltk")
>> Â x=(0:360)*pi()/180;
>> Â y=sin(x);
>> Â plot(x,y)
>> Â print -djpg figure-fltk.jpg
>> Â clear clg
>> Â graphics_toolkit("qt")
>> Â plot(x,y)
>> Â print -djpg figure-qt.jpg
>>
>>
>> In my system the plots are incomplete
>> (missing the upper and right portion)
>> and the print frezees octave requiring
>> a "kill -9 PID"
>
> On my test system all seems to work as desired. Full plots and no
> freezing of octave. Windows 7 x64. Newly downloaded and installed
> latest: octave, dbus.
> HTH,
>
> ..mark
>
thanks.
It seems an issue of the Intel Graphics driver.
When running with "startxwin -- -nowgl"
the plots are correct.
QT has still issue on window plot resizing
but the plots are correctly drawn.
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2018-12-27 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 8:59 Marco Atzeri
2018-12-27 10:01 ` Mark Geisert
2018-12-27 14:39 ` Marco Atzeri [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c5108e82-3cf5-371c-e6b2-6a3e03b9cec5@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).