On Wednesday 30 of November 2016 10:15:42 Michele Calgaro wrote: > On 2016/11/30 12:29 PM, Felix Miata wrote: > > man tdecmshell produces no manual entry. tdecmshell --help-all > > doesn't seem to show what I'm looking for AFAICT. > > > > What I'd like is to open 'tdemshell xserver', then run an xrandr > > command to change DPI, finally run 'tdemshell xserver' to compare the > > before and after impact from the xrandr command. It doesn't work. The > > second tdecmshell run simply focuses the original window. Is there > > any way to do what I want? If not, is it a feature that might be > > added to 14.1 if I filed a feature request bug? > > > > For now what I have to do as workaround is as shown here (using > > xterm) :-(: http://fm.no-ip.com/SS/dpi108vs133.jpg > > No idea what effort that would require, have to see how the software is > done. Wouldn't it be easier to open the first tdecmshell xserver, take > a snapshot, make the xrandr changes, then open the tdecmshell again and > compare? Just as a temporary workaround at least? > > Cheers > Michele I'm not sure whether is the ability to run two identical tdecmshell good idea. Most modules contain not only information, but mainly the settings. When will be opened two same settings, would be unsynchronized and saving settings could cause unwanted results. -- Slávek --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-devel-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
