On Thursday 05 July 2012 07:42:40 Martin Schreiber wrote:
> On Thursday 05 July 2012 06:13:25 IvankoB wrote:
> > in LINUX: change to mainfo.caption is reflected in GUI designer
> > in win-32: change to mainfo.caption will only reflect in run-time
>
> Can not reproduce. For me the design form or dat
On Thursday 05 July 2012 06:13:25 IvankoB wrote:
> in LINUX: change to mainfo.caption is reflected in GUI designer
> in win-32: change to mainfo.caption will only reflect in run-time
>
Can not reproduce. For me the design form or data modul window captions show
the form or data modul *name* not th
in LINUX: change to mainfo.caption is reflected in GUI designer
in win-32: change to mainfo.caption will only reflect in run-time
The people state that in LAZARUS the things are same in LINUX & win-32.
--
Live Security V
Hallo Martin,
Du schriebst am Sat, 17 Mar 2012 07:08:59 +0100:
> Then there is still the question wether
> "
>Option "Shadow" "True"
> "
> or
> "
>Option "DRI" "True"
> "
> or both fix the problem.
Although it might be moot by now (though there might be lazy guys like me
not having insta
Hallo Martin,
Du schriebst am Sat, 17 Mar 2012 07:08:59 +0100:
> > _Is_ there a separate "open source intel driver"? The way I read the
...
> Then probably I was mislead. So
> "
> Section "Device"
> Identifier "Device0"
> Driver "intel" <-
...
> actually loads "xf86-video-intel"?
I
On Friday 16 March 2012 20:29:15 Sieghard wrote:
>
> _Is_ there a separate "open source intel driver"? The way I read the
> information about the intel graphics chips is that the intel developped
> driver _is_ the open source driver, and the only one available at that.
> I looked for intel drivers
Hallo IvankoB,
Du schriebst am Fri, 16 Mar 2012 10:43:50 +0500:
> We still don't know which driver showed the bug.
> ==
> Is there a need for us to spend time on investigating a fixed 3-rd
> party driver bug ?
> (anyway, the "already-fixed" report was got form client guys not
> develo
Hallo Martin,
Du schriebst am Fri, 16 Mar 2012 07:22:38 +0100:
> I assume the "xf86-video-*" Intel proprietary driver showed the problem
> and the opensource "intel" driver works? Please confirm.
What's the difference?
> @Sieghard, did you try the opensource "intel" driver?
_Is_ there a separa
If it's "x86-video-intel" then yes :) Please note that Intel don't
provide only prebuilt (proprietary) drivers, they contribute to Xorg
sources instead.
(for Intel 845+ machines with integrated video, me use the
"intel915-dri" kernel mode framebuffer driver ( "Driver fbdev" &
"Option UseFBDev true
On Friday 16 March 2012 12:38:00 IvankoB for-mse wrote:
> It was *UPDATE* to "xf86-video-intel" driver - an open-source one
> contributed to Xorg by Intel engineers :)
>
>From an earlier mail from you:
"
The temp solution - creating /etc/X11/xorg.conf.d/20-intel.conf with:
Section "Device"
Id
It was *UPDATE* to "xf86-video-intel" driver - an open-source one
contributed to Xorg by Intel engineers :)
2012/3/16, Martin Schreiber :
> On Friday 16 March 2012 06:43:50 IvankoB for-mse wrote:
>> We still don't know which driver showed the bug.
>> ==
>> Is there a need for us to
On Friday 16 March 2012 06:43:50 IvankoB for-mse wrote:
> We still don't know which driver showed the bug.
> ==
> Is there a need for us to spend time on investigating a fixed 3-rd
> party driver bug ?
Yes it is. MSEgui users write "MSEgui does not work" not "my graphic driver
has bug
We still don't know which driver showed the bug.
==
Is there a need for us to spend time on investigating a fixed 3-rd
party driver bug ?
(anyway, the "already-fixed" report was got form client guys not developers )
2012/3/16, Sieghard :
> Hallo Martin,
>
> Du schriebst am Thu, 15 Ma
Hallo Martin,
Du schriebst am Thu, 15 Mar 2012 06:58:21 +0100:
> > Especially as the intel driver doesn't really shine on freeness from
...
> We still don't know which driver showed the bug.
Are there many of them? The intel-based machines I use, all are configured
to take the "xf86-video-i810"
On Wednesday 14 March 2012 22:14:26 Sieghard wrote:
> Hallo IvankoB,
>
> Du schriebst am Wed, 14 Mar 2012 22:40:06 +0500:
> > Has the bug been reported to the driver
> > makers?
> > ===
> > It has been too late (already fixed).
>
> It's always good to hear of a bug that it's too late to re
Hallo IvankoB,
Du schriebst am Wed, 14 Mar 2012 22:40:06 +0500:
> Has the bug been reported to the driver
> makers?
> ===
> It has been too late (already fixed).
It's always good to hear of a bug that it's too late to report it. ];->
Especially as the intel driver doesn't really shine o
Has the bug been reported to the driver
makers?
===
It has been too late (already fixed).
2012/3/14, Martin Schreiber :
> On Wednesday 14 March 2012 06:05:29 IvankoB for-mse wrote:
>> As reported, the Intel video issues are fixed in the latest Intel-DRI
>> version.
>>
> Which driver has
On Wednesday 14 March 2012 06:05:29 IvankoB for-mse wrote:
> As reported, the Intel video issues are fixed in the latest Intel-DRI
> version.
>
Which driver has problems (proprietary/open source)? Which one
works(proprietary/open source)? Has the bug been reported to the driver
makers?
Martin
-
As reported, the Intel video issues are fixed in the latest Intel-DRI version.
2012/3/10, IvankoB for-mse :
>> On Saturday 10 March 2012 10:27:44 IvankoB for-mse wrote:
>>> 1.Openbox - it's impossible to make form narrower than it was at the
>>> time when the form loaded. There's a feeling of if
> On Saturday 10 March 2012 10:27:44 IvankoB for-mse wrote:
>> 1.Openbox - it's impossible to make form narrower than it was at the
>> time when the form loaded. There's a feeling of if
>> bounds.cxmin=bounds.cymin=0 then somewhere bounds.cxmin turns into
>> bounds.cx & bounds.cymin into bounds.cy
On Saturday 10 March 2012 10:27:44 IvankoB for-mse wrote:
> 1.Openbox - it's impossible to make form narrower than it was at the
> time when the form loaded. There's a feeling of if
> bounds.cxmin=bounds.cymin=0 then somewhere bounds.cxmin turns into
> bounds.cx & bounds.cymin into bounds.cy respec
21 matches
Mail list logo
