headers
Adam Jimerson | 1 Sep 2011 02:29
Picon
Gravatar

Re: Where to report bugs for Vicious?

Thank you I made the suggested changes and it seems to be working just fine!

Jörg Thalheim wrote:
> Actually there is no bug tracker for vicious.
> If the following helps, I will make a commit.
> Add this between the "Grab enviroment" tags:
> 
> local math = {
> 	floor = math.floor
> }
> 
> ... and replace the line:
>    return { vol/0x10000*100, "on"}
> with:
>    return { math.floor(vol/0x10000*100), "on"}
> 
> Good luck.
> 
> 
> 2011/8/31 Adam Jimerson <vendion <at> gmail.com>:
>> In asking this I am assuming that bugs in Vicious widgets should be
>> reported outside of the bug tracker used by Awesome, if this is so where
>> should Vicious related bugs be reported?  My reason for asking this is I
>> am using the vicious.contrib.pulse widget to manage the volume of my
>> pulseaudio default sink, if the volume is anything other than o% or 100%
>> the volume level is treated more like a float than an integer. For
>> example according the the widget my sound cards volume is currently
>> 59.98535156225% instead of just rounding to say 60%.  Looking at the lua
>> code I see that it calls "tonumber()" on the value but it doesn't seem
>> to do the trick, unless tonumber doesn't convert decimal numbers to real
(Continue reading)

Permalink | Reply | 2 comments |
headers
Piotr Adamus | 1 Sep 2011 09:35
Picon

Re: Awesome 3.4 and Xrandr issue

Hello Pawel,

perhaps this is Linux- that's why it works beyond physics :)

Thank you for your help- maybe new update to libdlo and udlfb will
change that behaviour.

With kind regards.

Piotr.

On Wed, Aug 31, 2011 at 10:35 PM, Paweł <gorkypl <at> gmail.com> wrote:
> 2011/8/31 Piotr Adamus <panpiotradamus <at> gmail.com>:
>> Hi Pawel,
>>
>> Xinerama must be disabled- otherwise udlfb won't work at all. I spent
>> a whole week trying to figure it out how to get it working. It
>> eventually works, I can't complain but it could be even better :)
>>
>> I am attaching my current Xorg.0.log from working Intel and
>> Displaylink toghether.
>
> Well, it all looks quite weird :) I'm afraid I can't help you further
> - I would say it can't work this way, but if it works somehow... Well
> :)
> Anyway, I hope someday we'll get multiple graphics cards supoprt in
> RandR and such configuration will be as easy as it is currently with
> single GFX.
>
>> is it somehow possible to set an option in rc.lua that windows won't
(Continue reading)

Permalink | Reply | 5 comments |
headers
Jörg Thalheim | 1 Sep 2011 16:18
Picon

Re: Where to report bugs for Vicious?

I made the commit. It should be accepted in the next hour.

2011/9/1 Adam Jimerson <vendion <at> gmail.com>:
> Thank you I made the suggested changes and it seems to be working just fine!
>
> Jörg Thalheim wrote:
>> Actually there is no bug tracker for vicious.
>> If the following helps, I will make a commit.
>> Add this between the "Grab enviroment" tags:
>>
>> local math = {
>>       floor = math.floor
>> }
>>
>> ... and replace the line:
>>    return { vol/0x10000*100, "on"}
>> with:
>>    return { math.floor(vol/0x10000*100), "on"}
>>
>> Good luck.
>>
>>
>> 2011/8/31 Adam Jimerson <vendion <at> gmail.com>:
>>> In asking this I am assuming that bugs in Vicious widgets should be
>>> reported outside of the bug tracker used by Awesome, if this is so where
>>> should Vicious related bugs be reported?  My reason for asking this is I
>>> am using the vicious.contrib.pulse widget to manage the volume of my
>>> pulseaudio default sink, if the volume is anything other than o% or 100%
>>> the volume level is treated more like a float than an integer. For
>>> example according the the widget my sound cards volume is currently
(Continue reading)

Permalink | Reply | 1 comment |
headers
Alexander Yakushev | 1 Sep 2011 23:02
Picon
Gravatar

Awesome screencast

I decided to take a shot at making an Awesome screencast that may tell 
people about its basics. The first result is crappy as hell (especially, 
the sound) but I hope next parts would be better.
Briefly speaking, take a look and tell what do you think: 
http://www.youtube.com/watch?v=OZ_RVkAGf60
I think the second part would be about basic Awesome hotkeys, navigation 
etc., and in the third part configuration stuff can be highlighted. 
However any advices (concerning future screencast topics, mistakes and 
so on) from you are greatly appreciated.

Best regards.
Permalink | Reply | 12 comments |
headers
Julien Danjou | 2 Sep 2011 11:03
Gravatar

Re: Awesome screencast

On Thu, Sep 01 2011, Alexander Yakushev wrote:

> I decided to take a shot at making an Awesome screencast that may tell
> people about its basics. The first result is crappy as hell (especially, the
> sound) but I hope next parts would be better.
> Briefly speaking, take a look and tell what do you think:
> http://www.youtube.com/watch?v=OZ_RVkAGf60
> I think the second part would be about basic Awesome hotkeys, navigation
> etc., and in the third part configuration stuff can be highlighted. However
> any advices (concerning future screencast topics, mistakes and so on) from
> you are greatly appreciated.

This is a good idea, an the first part is nice.

Maybe new users can give you ideas of what they would like to learn, and
mid-level users could give you ideas about what they would have liked to
learn earlier. :-)

--

-- 
Julien Danjou
❱ http://julien.danjou.info
Permalink | Reply | 4 comments |
headers
Dieter Plaetinck | 2 Sep 2011 16:17
Picon

Re: Awesome screencast

On Fri, 02 Sep 2011 11:03:54 +0200
Julien Danjou <julien <at> danjou.info> wrote:

> On Thu, Sep 01 2011, Alexander Yakushev wrote:
> 
> > I decided to take a shot at making an Awesome screencast that may
> > tell people about its basics. The first result is crappy as hell
> > (especially, the sound) but I hope next parts would be better.
> > Briefly speaking, take a look and tell what do you think:
> > http://www.youtube.com/watch?v=OZ_RVkAGf60
> > I think the second part would be about basic Awesome hotkeys,
> > navigation etc., and in the third part configuration stuff can be
> > highlighted. However any advices (concerning future screencast
> > topics, mistakes and so on) from you are greatly appreciated.
> 
> This is a good idea, an the first part is nice.
> 
> Maybe new users can give you ideas of what they would like to learn,
> and mid-level users could give you ideas about what they would have
> liked to learn earlier. :-)
> 

Hi,
you should probably get a better microphone / use better settings / pay more attention to speak in a more
consistent volume or consistent distance from the microphone, or use a compresser to normalize the audio
volume differences.

Looking forward to your screencasts, but ones with good sound quality I hope, I couldn't understand some
parts of this one.
(Continue reading)

Permalink | Reply | 1 comment |
headers
David Henderson | 2 Sep 2011 16:20

Re: Awesome screencast

On 09/02/2011 10:17 AM, Dieter Plaetinck wrote:
> On Fri, 02 Sep 2011 11:03:54 +0200
> Julien Danjou<julien <at> danjou.info>  wrote:
>
>> On Thu, Sep 01 2011, Alexander Yakushev wrote:
>>
>>> I decided to take a shot at making an Awesome screencast that may
>>> tell people about its basics. The first result is crappy as hell
>>> (especially, the sound) but I hope next parts would be better.
>>> Briefly speaking, take a look and tell what do you think:
>>> http://www.youtube.com/watch?v=OZ_RVkAGf60
>>> I think the second part would be about basic Awesome hotkeys,
>>> navigation etc., and in the third part configuration stuff can be
>>> highlighted. However any advices (concerning future screencast
>>> topics, mistakes and so on) from you are greatly appreciated.
>> This is a good idea, an the first part is nice.
>>
>> Maybe new users can give you ideas of what they would like to learn,
>> and mid-level users could give you ideas about what they would have
>> liked to learn earlier. :-)
>>
> Hi,
> you should probably get a better microphone / use better settings / pay more attention to speak in a more
consistent volume or consistent distance from the microphone, or use a compresser to normalize the audio
volume differences.
>
> Looking forward to your screencasts, but ones with good sound quality I hope, I couldn't understand some
parts of this one.
>
> Dieter
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ryan T. Sawyer | 2 Sep 2011 17:09
Picon

Re: Awesome screencast

I had difficulty understanding the audio during most of this video. It
really needs revising or a different method of recording the voice
more clearly. Other than that, I must say that I really like
everything else. It stands out from other awesome screencasts on
Youtube in an exceptional way, is well edited, etc. Please continue to
share!

rts

On Thu, Sep 1, 2011 at 5:02 PM, Alexander Yakushev
<yakushev.alex <at> gmail.com> wrote:
> I decided to take a shot at making an Awesome screencast that may tell
> people about its basics. The first result is crappy as hell (especially, the
> sound) but I hope next parts would be better.
> Briefly speaking, take a look and tell what do you think:
> http://www.youtube.com/watch?v=OZ_RVkAGf60
> I think the second part would be about basic Awesome hotkeys, navigation
> etc., and in the third part configuration stuff can be highlighted. However
> any advices (concerning future screencast topics, mistakes and so on) from
> you are greatly appreciated.
>
> Best regards.
>
> --
> To unsubscribe, send mail to awesome-unsubscribe <at> naquadah.org.
>
Permalink | Reply | 0 comments |
headers
Piotr Adamus | 2 Sep 2011 21:16
Picon

Re: Awesome 3.4 and Xrandr issue

Hello Pawel,

I am just wondering. How is that possible if I run Xorg only on Intel
and two physical monitors Awesome somehow can recognize them and set
tag list separate per each monitor (so I use only one screen per
xorg.conf).

And if I use two screens (Intel and Displalink) awesome cannot
recognize anymore that I run two monitors?

How is that?

Kr.

Piotr.

2011/9/1 Piotr Adamus <panpiotradamus <at> gmail.com>:
> Hello Pawel,
>
> perhaps this is Linux- that's why it works beyond physics :)
>
> Thank you for your help- maybe new update to libdlo and udlfb will
> change that behaviour.
>
> With kind regards.
>
> Piotr.
>
> On Wed, Aug 31, 2011 at 10:35 PM, Paweł <gorkypl <at> gmail.com> wrote:
>> 2011/8/31 Piotr Adamus <panpiotradamus <at> gmail.com>:
(Continue reading)

Permalink | Reply | 4 comments |
headers
Jörg Thalheim | 3 Sep 2011 10:07
Picon

Re: Where to report bugs for Vicious?

Accepted...
http://git.sysphere.org/vicious/commit/?id=25b375bd6b8ee5ceb04d09fca2d8ba413850d278

2011/9/1 Jörg Thalheim <jthalheim <at> gmail.com>:
> I made the commit. It should be accepted in the next hour.
>
> 2011/9/1 Adam Jimerson <vendion <at> gmail.com>:
>> Thank you I made the suggested changes and it seems to be working just fine!
>>
>> Jörg Thalheim wrote:
>>> Actually there is no bug tracker for vicious.
>>> If the following helps, I will make a commit.
>>> Add this between the "Grab enviroment" tags:
>>>
>>> local math = {
>>>       floor = math.floor
>>> }
>>>
>>> ... and replace the line:
>>>    return { vol/0x10000*100, "on"}
>>> with:
>>>    return { math.floor(vol/0x10000*100), "on"}
>>>
>>> Good luck.
>>>
>>>
>>> 2011/8/31 Adam Jimerson <vendion <at> gmail.com>:
>>>> In asking this I am assuming that bugs in Vicious widgets should be
>>>> reported outside of the bug tracker used by Awesome, if this is so where
>>>> should Vicious related bugs be reported?  My reason for asking this is I
(Continue reading)

Permalink | Reply | 0 comments |

Gmane