tde-users

users@trinitydesktop.org

21 participants
4368 discussions

xsane crash
by Uwe Brauer 07 Dec '16

07 Dec '16

Hi I try to save a scanned document, which I have scanned with xsane. When trying to use a specific folder xsane crashes with the following message. [kcrash] TDECrash: Application 'xsane-gtk-tqt-application' crashing Years ago kgtk-qt3-trinity could cause certain applications to crash, but kgtk-qt3-trinity is not installed. Could it be something similar? Regards Uwe Brauer

2 1

Displaying QMap objects in a dialog
by Leslie Turriff 06 Dec '16

06 Dec '16

The application I'm writing will have a small group of key-value pairs associated with each object. Looking through the docs, I see widgets for displaying elementary items (e.g. TQListBox), but nothing for something like a TQMap (e.g. a TQlistBoxMap). I could use a TQTable, but that strikes me as akin to using a sledgehammer to kill flies. As a neophite c++ programmer, I know that in theory I can subclass TQListBoxItem to do this, but how to go about that, I haven't a clue. The docs say merely that ' If you need to insert customized items into a TQListBox you must inherit this class and reimplement paint(), height() and width().' Any suggestions to help get me started with this would be appreciated. Leslie

2 2

Struggling with "C++ GUI Programming with Qt 3"
by Leslie Turriff 05 Dec '16

05 Dec '16

Hi, I'm trying to learn to write a GUI app using the book "C++ GUI Programming with Qt 3", which of course is not written with Trinity in mind, but hopefully will be enough to get me started. I've already figured out that I need to substitute 'tqmake' for 'qmake', but I can't get the simple 'helloworld' project to actually compile the c++ code. I've got the project generated, and I see the code in its src/ directory, but when I try to build it (the book says to use 'make') it says "make: Nothing to be done for 'first'." Here is the Makefile generated by tqmake: > > ########################################################################### > Makefile for building: Tutorial1 > Generated by qmake (1.07a) (TQt 3.5.0) on: Wed Nov 16 22:57:35 2016 > Project: Tutorial1.pro > Template: subdirs > Command: $(QMAKE) -o Makefile Tutorial1.pro > ########################################################################### > > MAKEFILE = Makefile > MAKE = tqmake > DEL_FILE = rm -f > CHK_DIR_EXISTS= test -d > MKDIR = mkdir -p > INSTALL_FILE= > INSTALL_DIR = > SUBTARGETS = > > first: all > > all: Makefile $(SUBTARGETS) > > Makefile: Tutorial1.pro /usr/share/tqt3/mkspecs/default/qmake.conf > $(QMAKE) -o Makefile Tutorial1.pro > qmake: qmake_all > @$(QMAKE) -o Makefile Tutorial1.pro > > all qmake_all distclean uicables mocables install_subdirs uninstall_subdirs uiclean mocclean lexclean yaccclean clean : FORCE > install: install_subdirs > > uninstall: uninstall_subdirs > > FORCE: > And here is the Project file: > ###################################################################### > # Automatically generated by qmake (1.07a) Wed Nov 16 22:47:58 2016 > ###################################################################### > > TEMPLATE = subdirs > > # Directories Are there additional steps required when compiling a QT project in Trinity? Leslie

7 21

How to make kmail bottom-post by default?
by Leslie Turriff 03 Dec '16

03 Dec '16

Is there a way to tell kmail to do this? Leslie

4 9

Dolphin
by Baron 03 Dec '16

03 Dec '16

Hi Guys, PcLinuxOs, Trinity 14, I think I might have stumbled on a bug ! I've had folders seem to disappear when moved from one window to another. I've found that if there are more folders than can be displayed in the window, moving down to the bottom of the window so that the top folders cannot be seen, and then moving a folder from another window into the white space, results in the moved folder disappearing. Doing a find tells me that the missing folder is now in one of the folders above and not in the white space where I put it or in the sort order. If I move to the top of a folder with files below the bottom and If I move and put a folder from another window at the top but between the others it goes where I put it. It works as expected. I can repeat this every time. Note the folder sort is set to "By Name" I mention this because I thought that "Sort" might have something to do with it, but it doesn't seem to. Thanks Guys. -- Best Regards: Baron

3 3

Re: [trinity-users] Re: Re: Dual screen setup not remembered
by midi-pascal 01 Dec '16

01 Dec '16

Thank you! Inspired by your scripts and the output of xrandr, two lines in my .bashrc did the job: xrandr --output HDMI-0 --right-of DVI-0 --auto --primary xrandr --output DVI-0 --auto I over-simplified the commands because I am on a desktop and my two screens are always connected. No more fiddling with screen settings on each login! :-) On 16-12-01 03:00 PM, deloptes wrote: > iadest(a)o2.pl wrote: > >> OK, this is a sum of 3 scripts I use: >> >> #!/bin/bash >> >> #Test if we are not in dock >> if [ -a /dev/video0 ] >> then >> #echo "Going to dock mode!"; >> xrandr --output LVDS1 --off >> #xrandr --output VGA1 --mode 1600x1200 >> xrandr --newmode "1600x1200b" 180.0 1600 1604 1796 2050 1200 >> 1201 1204 1250 +hsync +vsync >> xrandr --addmode VGA1 1600x1200b >> xrandr --output VGA1 --primary --mode 1600x1200b >> xrandr --addmode DVI1 1600x1200b >> xrandr --output DVI1 --mode 1600x1200b >> xrandr --output DVI1 --right-of VGA1 >> else >> #we are not in dock. Check do we have output on VGA >> >> if [ -n "`xrandr | grep \"VGA1 conected\"`" ] >> then >> #echo "Going to projector mode!"; >> xrandr --output LVDS1 --mode 1024x768 --output VGA1 >> --mode 1024x768 --same-as LVDS1 >> fi >> fi >> >> There may be problems with newlines. "1201 1204 ..." is the continuing >> of previous line. "--mode 1024x768 --same-as LVDS1" is also in previous >> one. >> >> WARNING: Do not use this script directly on Your monitor without >> checking. High frequency may damage the monitor, especially old CRTs. >> >> So what I'm doing there: first I check for availability of my tuner >> card, this card is installed in dock. It computer is in dock, I: >> 1. Turn the LCD off >> 2. Set a custom 1600x1200 mode (here called "1600x1200b" for my >> monitor which is connected through Sun-VGA adapter and X has no idea >> how to handle 1600x1200 on it. >> 3. Activate it as primary. >> 4. Activate the second display (DVI) as the one right of VGA monitor. >> If I'm not in dock, I look for something connected to VGA port. >> If there is, LCD gets down to 1024x768, and VGA copies it. >> >> MCbx >> >> Gerhard Zintel <gerhard.zintel(a)mrs-thomas.de> >> napisał(a): >> >>> On Thursday 01 December 2016, deloptes wrote: >>>> iadest(a)o2.pl wrote: >>>> >>>>> Maybe this solution is not official and proper one, but works: >>>>> Put the xrandr commands in a shell script and execute is at >>>>> startup. >>>>> >>>>> I have such script which detects is my notebook docked first. If >>>>> yes, dual-screen configuration for dock outputs are set and >>>>> notebook's LCD is turned off. >>>>> If it's not docked, script checks for display connected to VGA >>>>> port. If it is, it duplicates screen from notebook decreasing >>>>> resolutions to 1024x768 as it's usually a projector in a lecture >>>>> room and it can't do more. >>>>> MCbx >>>> I do the same. In the office I have two additional monitors and at >>>> home one. So a shell script is checking what is available and runs >>>> xrandr to setup the monitor and resolution. >>>> Perhaps this is the reason we never noticed that the settings are >>>> not saved and/or applied at tde session startup. >>>> In fact I have noticed this on a VM ware recently, but I was >>>> thinking it has to do with the vmware. >>>> I think it is worth a bug report, so that we may not forget to >>>> inspect this. >>> Can one of you guys please share that kind of shell script here on >>> the list to give me a clue how to start? >>> >>> Gerhard >>> > SCREEN=`xrandr | egrep "[[:space:]]connected[[:space:]]" | grep -v eDP1` > if [[ "x"$SCREEN != "x" ]] > then > xrandr --output $SCREEN --right-of eDP1 --auto > xrandr --output eDP1 --off > else > xrandr --output eDP1 --auto > fi > > eDP1 or LVDS depends on your card - look into the driver manual > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net > For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net > Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ > Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting > >

1 0

Dual screen setup not remembered
by midi-pascal 01 Dec '16

01 Dec '16

Hi, I use Trinity R14.0.4 under Ubuntu 14.04 on a Dell Optiplex 990. My setup is dual screen (1 HDMI 27po, 1 DisplayPort 24 po) connected to a Radeon video card. The 24po is on my left and the 27po is in front (main screen). I tried tderandrtray, Trinity Control Center, System Settings to set things up with success. But each time I log out or reboot, the display settings are lost. Both screens show the same display (main) and are in reverse order (left/right). Is there a way to make Trinity remember my screen settings so I do not have to set things up each time? Thanks!

6 8

Directory depth
by Baron 28 Nov '16

28 Nov '16

Hi All, Quick question. 32 Bit LinuxOS, Trinity 14.0. Is there a limit to directory depth ? if so what is it. Thanks. -- Best Regards: Baron

5 13

Can't install on Opensuse Leap 42.2
by Ian Gay 27 Nov '16

27 Nov '16

Attempt to install trinity-desktop on Opensuse Leap 42.2 fails with message Problem: trinity-desktop-14.0.4-1.oss422.noarch requires trinity-tdeaccessibility >= 14.0.4, but this requirement cannot be provided Attempt to install trinity-tdebase fails with message Problem: nothing provides libHalf.so.12()(64bit) needed by trinity-tdelibs-14.0.4-1.oss422.x86_64 What to do?

2 2

Struggling with (T)QT3 tutorial
by gregory guy 27 Nov '16

27 Nov '16

Hi there! Not sure if It"s the right thing to do, but I adjusted tutorial 1 code (hello world) like this: ------------------------------------------------------------- #include <tqapplication.h> #include <tqpushbutton.h> int main( int argc, char **argv ) { TQApplication a( argc, argv ); TQPushButton hello( "Hello world!", 0 ); hello.resize( 100, 30 ); a.setMainWidget( &hello ); hello.show(); return a.exec(); } ------------------------------------------------------------ Since I've compiled Trinity by myself the headers are located in /usr/include/tqt and /usr/include/tqt3, the libraries (all of them) in /usr/lib64. I had to adjust the Makefile file accordingly, like this: --------------------------------------------------------------------------------------------------------------------- INCPATH = -I/usr/share/tqt3/mkspecs/default -I. -I/usr/include/tqt -I/usr/include/tqt3 LINK = g++ LFLAGS = -luuid -Wl,-rpath,/usr/lib64 LIBS = $(SUBLIBS) -L/usr/lib64 -L/usr/X11R6/lib -luuid -ltqt-mt -lXext -lX11 -lm -lpthread --------------------------------------------------------------------------------------------------------------------- Hope that help!

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

tde-users