World: r3wp

ok, well I use a 1280x960 resolution. When I want to move one page 
up in the View group, it moves up one page and one line, meaning 
I miss a line of text. This effect gets worse, the bigger the group 
is.

however it moves a page up correctly in this group

I have a 500 message limit

you could also make the window smaller for this group. Page scrolling 
scrolls about two pages if the size of the list is about 2-300 pixels.

OK, I have the same resolution, but when I move teh scroll wheel 
one click, it moves the window up one line.  What is the diff between 
our systems?

If I click on the up and down arrows it moves one line as well.


So I went into Controls, Mouse, Scroll, and changed it from Slow 
to fast, and can reproduce what you guys are saying.....................so 
again I state, this is not an AltME (or Rebol) problem per se, but 
appears to be a Windows settings issue you can change.

This is not to say there is not a bug in VID or something.  It may 
be that Rebol needs to calibrate something differently

I rarely use the arrow buttons. I click in the empty area in the 
scroller to move the scroller up and down one page at a time.

When I do that (which I have never done before for the record), I 
see Ingo's post at the top "The other thing is".  When I click in 
the empty space I see "part of " Ingo's other post (right above the 
first) "I've only had")


This is not a test you can reproduce now, but...................I 
can see that the scroll area is missing a page and .5 ines.  This 
would seem to be the nature of Robert's statement.


Is this what you all are doing?  Pressing in the empty space of the 
scroll area?

Currently my top post is Henrik "well I use 1280x960", clicking the 
up arrow, my bottom post is Ingo "You mean message number in AltME?" 
 My window is about 3/4 width and height of 1024x768  My message 
limit is 1000 (I was looking for an older post).

I can see the intermediary messages by dragging the scrollbar (has 
to be precise).  I don't have a scrollwheel to hand right now.

Switching to 300 messages improves the situation, but the up arrow 
skips over half a page, not one line.

reichart, I think that's what we are doing, and I actually first 
observed the problem with one of my users and then another and another...


The scroller knob looks like it's moving a full page, but it's really 
not. I think this is because the page size is derived directly from 
the pixel size of the knob, which will cause rounding errors, the 
smaller the knob gets.

Hmmmm.  so I set my message max to 100.  So I always have a big thumb 
(the scroll bar is called a thumb for the record).  So the question 
still stands, how to solve the problem.

Lie to Rebol UI perhaps?

Lie as in not tell the truth? :-) Perhaps it would be best to fix 
the scroller at the source of the problem.

That assumes there is a "source"  This could be that the wrong value 
is being sent to the scroller.  Hard to tell.  What we need to do 
is have a scroll example that works with all conditions.  Then we 
will use the same values for ours.

I see the problem as this:

* Line and Page steps should be fixed units, based on text line height 
and containing face height respectively.

* The position of the 'thumb' in the shaft should be determined by 
the position of the content relative to the container, not vice-versa 
(only exception is when dragging the 'thumb').

* Clicking on the empty shaft area should page scroll, the arrows 
should line scroll.

* Using the scroll-wheel for line scrolling can be multiplied by 
the system setting.

Agreed.

Ok, I have always set my mouse to the fastes movement possible on 
the system. I don't use a scroll-wheel, I just click the arrows to 
either go line-by-line or posting-by-posting (which I would prefer). 
But, as Chris stated, clicking ones, pages more than one page up/down, 
so I'm missing postings. Workaround: Dragging the slider, which is 
a mess with this mouse speed and the number of messages (IIRC 1500) 
I display.

RE: "The funny thing is………………."  Me thinks Altme knows who to freak 
out on. : ) The great thing is that I have everything back.

: )

I just received a response back from support in regards to changing 
the password of a World (not a user). 

AltME world passwords can not be changed in this release.  If it 
could be changed, the user would have to do that.
 

IMHO that should be changed as there may be times where this is necessary.

Right, hence the statement was "in this release."

We will get better and better at this stuff.

I know you will : )  Thanks.

:)

Wargh!  Invalid recycle!

...sorry...

When it rains, it snows

Invalid datatype during recycly, repeatedly, if I go to the chat 
group directly after start of altme. Let's see, if it remains the 
same after this post ...

yes, still so ... now If we had kind of debug mode, to track it down 
....

btw - is altme 1.1.28 based upon latest SDK? (I mean, kernel fixes?)

installed 1.2.5, and it is ok now ....

1.2.5 is based on latest sdk (ie view 1.3), while 1.1.28 is still 
based on view 1.2.

can I install 1.2.5 into my current 1.1.28 install without losing 
any thing ?

i did. but, it's always a good idea to have a backup.

I did so too, everything seems to work ok ...

Same, if something went wrong it was a minor hiccup.

worked just fine :)

is anyone else having their XP altme client "freeze up" after receiving 
a single message?

this started happening to me on one machine yesterday  (after MS 
updates)  
a world server on the same machine continues to work.

No, Altme working OK. But I do have some odd behavior with an rebol 
encap'd .exe running from the shared files in Altme. When I exit 
the program with the windows "X" close button the app's window closes 
but the app stays around as a task.

..that has to shut down in task mgr.

Recently (several weeks ago) we had masive crashes here after a MS 
update on diff computers.

However, AltME seems fine on my two XP laptops (diff designs and 
versions).

james: "When I exit the program...the app's window closes but the 
app stays around as a task"

hmm..does this your encapped program only when running from altme 
or als when you run it 'normally'?

If the second is true maybe you are using in your program something 
like:
view/new layout [...some layout here...]
forever [
	do [...some loop code...]
	wait <some time> 
]


If so the you need to properly handle the event when you closing 
the View window because othervise the window is only closed but the 
FOREVER (or any other) loop is still running. The solution is for 
example put before the "view/new" line:


insert-event-func func [face event][if event/type = 'close [quit] 
return event]


(ofcourse if your app is using multiple windows you need to add some 
more logic to decide which window should QUIT the app and which not 
when using the 'X' close button)

Thanks Cyphre. I believe with this app, this is the case as it is 
able to be launched from another script and then return to that script. 
Good catch. I will fix that. dekuji vám!

:-)

To think I had all those instances running all this time!

What about some easy way how to localize Altme?