David Tweed | 6 Dec 13:30 2004
Picon
Picon

description of behaviour of floating splits vs standard frames

Hi,

I'm currently working on an fltk based (www.fltk.org) program which
launches new windows. It's crashing in a mysterious way. I'm extending
some of the existing widgets and it's probably down to some
misunderstanding somewhere in my extension code, but to track down what's
wrong I'll probably need to ask on the fltk lists, specifying what Ion3 is
doing in terms of X notifications; to do that I'll have to ask here to
find out a rough idea of what that is myself :-)

If I run my program on a normal frame based workspace it doesn't crash no
matter how many new windows I create. If I run my program in a floating
split workspace it crashes within the first one/two window creations (90%
of time on creating first new window, 10% of time creates first window ok
but crashes trying to create the second). Could anyone give me a quick
overview of what Ion3 does differently in the floating split vs
standard split case? (It crashes somewhere in the Fl::handle routines, 
which are the way fltk handles various events like mouse clicks, keyboard, 
etc... on what looks like the event 3==FL_ENTER, which I think means 
"mouse ptr wasn't previously over window, is over window now".)

Many thanks for any helpful commentary,

PS: a quick question regarding behaviour of latest Ion3 snapshot: if I
move a window by dragging a tab from one frame to another with the mouse
(doesn't matter if standard or floating split) it looks like the frame
dragged to has become the current frame (in terms of its colours).  
However, if a new process/window is launched (eg by the newly dragged
window) it appears in the frame the window was dragged from, whereas it
seems to me personally more intuitive that it would appear in the frame
(Continue reading)

Tuomo Valkonen | 7 Dec 16:44 2004
Picon
Picon

Re: description of behaviour of floating splits vs standard frames

On Mon, Dec 06, 2004 at 12:30:37PM +0000, David Tweed wrote:
> Many thanks for any helpful commentary,

Nothing should IIRC be done differently when starting to manage windows.

> PS: a quick question regarding behaviour of latest Ion3 snapshot

Fixed.

--

-- 
Tuomo

Noah Slater | 9 Dec 19:52 2004
Picon

ioncorelib not in search path

Hello,

I am running Debian GNU/Linux and installed Ion with APT. This worked
fine but the apt package was not up to date - so for this reason I
chose to download and compile from source from the official website.

Everything worked fine, but when I try to start Ion at login it fails
with a message similar to:

'ioncorelib not in search path'

I do not understand this as ioncorelib.lua installed itself into
/usr/local/share/ion and I have tried to symlink various folders
around but nothing works. I even added a few extra lines in my bashrc
file and double checked permissions on said files.

Nothing. Nada.

It would be helpful to know what Ion 'thinks' the search path is so I
can rectify the problem - I've lost patience trying to guess.

Ion looks like the best WM out there and I would appreciate someone
nudging me in the right direction so I can crack on and start using
it!

:D

Thanks,
Noah

(Continue reading)

Andreas Bernauer | 10 Dec 11:04 2004
Picon
Picon

Re: ioncorelib not in search path

Hi Noah,

Noah Slater wrote:
> Everything worked fine, but when I try to start Ion at login it fails
> with a message similar to:
> 'ioncorelib not in search path'

I had a similar problem when I installed ion-2 to my home directory.
I also had to guess around a while, as the error messages where not
very helpful for me.  The following resolved the issue for me.

I start ion2 with the following command in my ~/.xsession

------>

#!/bin/sh

exec $HOME/root/bin/ion -confdir $HOME/root/etc/ion -confdir $HOME/.ion2 -confdir
$HOME/root/share/ion -moduledir $HOME/root/lib/ion

<-------

IIRC, the order for the confdirs was important and the last option had
to be moduledir (but I am not sure on that one).

Maybe this helps you.

--

-- 
Andreas.

(Continue reading)

Noah Slater | 10 Dec 12:19 2004
Picon

Re: ioncorelib not in search path

Thanks for your reply!

Actually after chatting on the IRC channel with a very helpful person
who's nick escapes me I got to the root of the problem.

For some reason 'make install' had touched some of the ion dirs with
the oddest set of permissions - something along the lines of 'root
root 770'.

Very odd. In the end, all I did was run strace and work my way through
all the dirs in the paths it was searching manually repairing
permissions.

Perhaps you should should take a look at your installation as well. If
this is a problem that effects more people than just me it might need
to be addressed.

Noah

On Fri, 10 Dec 2004 11:04:48 +0100, Andreas Bernauer
<andreas.bernauer <at> gmx.de> wrote:
> Hi Noah,
> 
> Noah Slater wrote:
> > Everything worked fine, but when I try to start Ion at login it fails
> > with a message similar to:
> > 'ioncorelib not in search path'
> 
> I had a similar problem when I installed ion-2 to my home directory.
> I also had to guess around a while, as the error messages where not
(Continue reading)

Elvelind Grandin | 10 Dec 12:44 2004
Picon

paste tip,

Hi.

sometime ago there was a thread on the problem with pasting in a xterm
when the cursor was on the title rather then in the window.

if you use aterm you can set pasteMouseOutside: true to resolv that.

cheers.
elvelind grandin

Noah Slater | 10 Dec 12:53 2004
Picon

Bug? Ion shuts down when initial xterm is closed

Hello,

The most annoying thing just wasted about 30 minutes of my time and I
still cant get it fixed.

I am using Ion2 and I compiled from source yesterday from the official site.

When Ion starts up it presents me with an initial xterm. I spent quiet
some time arranging windows, opening applications and setting up my
work environment.

At the end of all of this the original window with the first xterm had
ended up at the bottom of the screen in a nice little square - so i
ran 'xclock &' and was finally happy everything was ready to go.

The xterm spawned a new tab in the same window which contained now
xclock. I went to close the xterm tab as it was no longer needed and
the whole of Ion shut down and logged me out.

This is repeatable and it doesn't seem to matter which method you
choose to close the xterm. All that seemingly matters is that the
window/tab you must close is the original xterm you were presented
with at login.

This is unexpected behaviour on my part and I am preying it is not a 'feature'.

Could someone either tell me why this happens, how to stop it, or
confirm that it is in fact a bug.

Thank you for your time.
(Continue reading)

Philipp Grau | 10 Dec 13:14 2004
Picon
Picon

Re: Bug? Ion shuts down when initial xterm is closed

Hello, 

* Noah Slater <nslater <at> gmail.com> [10.12.04 12:53]:
> When Ion starts up it presents me with an initial xterm. I spent quiet
> some time arranging windows, opening applications and setting up my
> work environment.

How did you start your X11-Session? 

My is started with a small .xsession script, simply starting ion:

/path/to/ion

keeping ion in foreground.

It looks like you were starting your session with an xterm a last process.
And then starting ion within this window in background. So quiting the xterm
will kill ion.

Have a look at yout startup sequence

Philipp

Tuomo Valkonen | 10 Dec 13:15 2004
Picon
Picon

Re: Bug? Ion shuts down when initial xterm is closed

On Fri, Dec 10, 2004 at 11:53:22AM +0000, Noah Slater wrote:
> I went to close the xterm tab as it was no longer needed and
> the whole of Ion shut down and logged me out.

Are you sure you're not starting the xterm after Ion in your .xsession
(or whatever)?

	ion &
	xterm

will result in the kind of behaviour you described. You should instead
have

	xterm &
	ion

--

-- 
Tuomo

Noah Slater | 10 Dec 13:27 2004
Picon

Re: Bug? Ion shuts down when initial xterm is closed

Hi,

Thanks for your help, I'm a bit of a newbie to all of this. The
contents of my .xsession file are as follows:

#!/bin/sh
xterm &
exec ion

So it would appear that you have quite skillfully got to the bottom of
my problem. My .xsession has now been changed to

#!/bin/sh
exec ion

I have not had a chance to test this but I am fairly certain the
problem has now been addressed - I will let you know if it's not.

Thank you so much for your help!

Noah

On Fri, 10 Dec 2004 13:14:35 +0100, Philipp Grau
<phgrau <at> cis.fu-berlin.de> wrote:
> Hello,
> 
> * Noah Slater <nslater <at> gmail.com> [10.12.04 12:53]:
> > When Ion starts up it presents me with an initial xterm. I spent quiet
> > some time arranging windows, opening applications and setting up my
> > work environment.
(Continue reading)


Gmane