On Wed, Jul 23, 2014 at 4:20 AM, P L. Lucas <sela...@gmail.com> wrote: > Hi, > > Sorry, but I'm not good in English.
Don't be sorry. I'm not a native English speaker, either. Your English is just as "good" as mine. :) > I'm trying to reproduce that bug. I have found that "Unify" doesn't > work. Using monitors options, finally I could work with both monitors. > > I added virtual resolutions to lxqt-config-randr and code is very > complicated. There are old functions that can be erased because they > are not called. A refactor of lxqt-config-randr code is needed. That's absolutely right. A serious refactor is obviously needed. However, currently nobody can do it. I know very little about XRandR, and we fail to get in contact with its original developer. So we get stuck here. XRandR caused various bugs, especially those related to desktop manager and panel. We definitely have to fix that before 0.8 release. > You (PCMan) wrote lxrandr-qt: > > https://github.com/PCMan/lxrandr-qt Yes, but I deprecated that and start using lxqt-config-randr instead. The UI of lxqt-config-randr just looks nicer and it's feature rich. AFAIK it's ported from KDE. > lxrand-qt is simple and xrandr based. > I started to implement virtual resolutions in lxrandr-qt and I added a > simpler XrandR protocol implementation: > > https://github.com/selairi/lxrandr-qt > > It uses XrandR protocol (API) to get monitor info. Settings are done > with xrandr command. Looks good, but parsing the output of xrandr has some benefit. 1. No hard dependency or linkage to xrandr libraries. 2. Let xrandr developers handle the differences among different versions of XRandR. We don't need to touch that. 3. It's possible that the output of xandr might be changed in newer versions, but we can handle that easily with regular expression. 4. If we really need to check the version of xrandr, we can call "xrandr --version" to obtain that info. 5. We don't need to know much about XRandR. We only need to know basic regexp and simple string parsing. > PCMan/lxrandr-qt reads monitor config from a pipe to xrandr. This > output is human readable but it can change easily. > > Maybe we could back to lxrandr-qt and start to refactor lxqt-config-randr. I'm OK with any option given it works correctly. For now, if we cannot fix lxqt-config-randr, I agree that we can use lxrandr-qt first. Besides, we can actually make it part of lxqt-config instead of maintaining a separate package. > Question. I don't know Wayland. Which tool does Wayland use to config screen? AFAIK, you cannot do that yet. I don't know any xrandr equivalent for wayland. It's a long way to go before Wayland become really usable for desktops. > Thanks. > > 2014-07-20 15:29 GMT+02:00, PCMan <pcman...@gmail.com>: >> Hello, >> I just noted that lxqt-config-randr is broken. >> When I plugged in an external monitor, set set its content a clone of >> my laptop's monitor, it failed to work. >> My external monitor became blank and only showed a cursor. >> If I restart X11, and do the same using the command "xrandr --output >> VGA-0 --same-as LVDS", then everything works. >> I tried to dig into the code of lxqt-config-randr, but it's really >> complicated. >> I can't understand the XRANDR part and have no idea why it does not work. >> So, zballinita do you know what's wrong with it? >> >> Besides, I'd like to replace all of the complicated XRandR code in >> lxqt-config-randr with calls to external command line tool "xrandr", >> just like what we did in lxrandr in old lxde. >> Relying on an external tool is not cool, but this has some significant >> benefit. >> * We don't need to maintain all of the XRandR code. >> * We only need to do simple string parsing for the output of xrandr, >> and compose a new xrandr command line and execute it. extremely >> simple! >> * We can reuse xrandr and let its developer maintain the RandR part. >> If in the future there are changes in the RANDR spec, we're not >> affected. >> * We don't have to link to libXlib and XrandR. This may benefit >> wayland support in the future. >> * xrandr is light and correctly implemented. We can launch it on >> session startup to configure the monitors. This is lighter than >> launching lxqt-config-randr. >> >> What do you guys think? >> If there're no objections, I really want to try to do it (in a >> separate branch, of course). >> >> ------------------------------------------------------------------------------ >> Want fast and easy access to all the code in your enterprise? Index and >> search up to 200,000 lines of code with a free copy of Black Duck >> Code Sight - the same software that powers the world's largest code >> search on Ohloh, the Black Duck Open Hub! Try it now. >> http://p.sf.net/sfu/bds >> _______________________________________________ >> Lxde-list mailing list >> Lxde-list@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/lxde-list >> ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Lxde-list mailing list Lxde-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxde-list
