rejetto forum

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - joxy

Pages: 1 2 3 4 5 6
46
&RQ / bugs
« on: May 13, 2002, 01:13:30 PM »
Quote
joxy: I don't currently know what exactly makes it appear from its hidden state.

rejetto: are you sure that is appears always-on-top and not simply on-top ?

Well, I am not sure, but still: in these situations, it is hidden, and it should remain hidden... but it becomes visible (and (onTop or alwaysOnTop)).

I will try to answer your 'are you sure' question later.

47
&RQ / Feature requests (FRs)
« on: May 13, 2002, 08:33:31 AM »
Also, ESC could hide the contact list window.

48
&RQ / Feature requests (FRs)
« on: May 13, 2002, 08:26:16 AM »
I found a good enough argument to implement the following:

"ESC could close any dialog." [joxy]

Previously, rejetto answered with: "hmmm, not sure this is good, sometimes ESC could trigger some other action, and there is already a hotkey for close (that is alt+f4). so, does it worth?"

----------------

One second ago I thought that there is a "MS Windows GUI guidelines" document by Microsoft (can be found somewhere on their site).  And, I am almost sure that my guess is right:  that document probably specifies the "close dialog" action for ESC key as a common Windows GUI standard.  (I haven't read that MS guidelines doc.)

Final decision will, yes, be done by rejetto.

49
&RQ / bug
« on: May 08, 2002, 09:00:31 AM »
When 'contact list always on top' option is off, then sometimes (on misc. incoming events(?) (which don't have a 'pop up' option specified)), the hidden contact list sometimes appears and becomes always on top.  

I don't currently know what exactly makes it appear from its hidden state.

50
&RQ / bug in icq server - workaround in &rq0849 needed
« on: May 08, 2002, 06:13:55 AM »
When i leave client logged in at office, and then go home and login there, the client instance at office shows 'logged on from another location' dialogbox, and does not disconnect.  Then, remote user sends me a message.  This message arrives to an office client instance; I don't see it at home.

Proposed workaround: &rq should disconnect immediately when received the 'logged on from another location' error code.

51
Developers / Layouts
« on: April 23, 2002, 09:20:36 PM »
Well.  I had some time, and tried to prepare my own russian translation (I will not use it; just for entertainment.)

Since russian wording is generally 1.5...2 times lenghtier than the english one, most of translations don't fit into their places.

I can submit my (incomplete) translation, just for rejetto to have a look.

52
&RQ / Feature ideas (FIs)
« on: April 16, 2002, 12:32:25 PM »
In the contact list context menu, add the checkbox "show only people you are visible to".  Thus, one will be able to hide all unwanted folks.


 

53
&RQ / color scheme suggestion
« on: April 10, 2002, 01:16:40 PM »
I suggest the following color scheme for &rq users:

In the chat window, click "Preferences" button

My font & his font color: Maroon
Background color: red 250, green 250, blue 241



Edited by - joxy on 04/11/2002  00:33:56

54
&RQ / Temporary workarounds for bugs
« on: April 03, 2002, 07:22:06 AM »
Bug in &rq 0.8.3.2: Sometimes, when you delete message in the history, the history gets corrupted.  When this occured, you see the msgbox "history is corrupted, some data is lost" when you push "Show the whole history" button in the bottom of the chat window, or maybe also (I am not sure) even when you just send or receive a message or status change event.

Workaround1: Do not use "history -> right-click menu -> delete" feature.

Workaround2: If your history got damaged, you can repair it using any hex editor application.

History format (sent to me by rejetto):

- history file is a sequence of message records;
- message record starts with 4 bytes of 0xff;
- after these 4 bytes of 0xff there is 1 byte that is the type of the message (e.g. 0x01 for normal message);
- after the message type, there is the uin of the sender;
- and so on.

Instructions to repair the history file:

1. Close &rq application.
- In the hex editor, open the history file for your buddy.
- Scroll to the end of the file.
- Find start of the message.  To do this, find 0xff 0xff 0xff 0xff backwards.
- You can skip several messages.
- Truncate the file at the position of the 0xff 0xff 0xff 0xff sequence (so that this 0xff 0xff 0xff 0xff will get rejected, and the last byte of the file will become not equal to 0xff).
- Launch &rq, open the chat window with the buddy that caused the error.  Hit "Show the whole history" button.  If the history is still corrupted, try removing another several messages.  To do this, repeat this entire procedure from the step 1.




Edited by - joxy on 04/03/2002  09:24:57

Edited by - joxy on 04/03/2002  09:25:52

Edited by - joxy on 04/03/2002  09:26:20

55
&RQ / Bugs
« on: April 03, 2002, 01:29:10 AM »
In "Preferences - Events - event: message", when I turn "pop up chat" on, and exit & relaunch &rq, the "pop up chat" is off.  This is stable behavior.

 

56
&RQ / Feature requests (FRs)
« on: March 19, 2002, 07:34:35 PM »
FR1

https:// urls could be clickable.

FR2

numbers >= 5 digits could be clickable, too, to add a icq uin to a current contact list

FR3

double-click on the url could spawn a browser (just like a signle click)

right now, it spawns the browser PLUS opens a chat message text window.  This behavior is IMO inconvinient.





Edited by - joxy on 03/19/2002  20:41:45

57
&RQ / Bugs
« on: April 21, 2002, 08:59:19 AM »
bug
when i insert a text 8184 bytes long and hit CtrlEnter, &rq doesn't warn me, but tries to send it.  The server disconnects it.  &rq reconnects.

&rq should not attempt to send > 7000 bytes (which is a limitation of standard clients icq2000x).

 

58
&RQ / Bugs
« on: April 16, 2002, 03:02:25 PM »
terribel bug

i had "ignore oncoming/offgoing events if faster than" option turned on,
and then decided to turn it off, and turned off.  When pressed OK, I had
an access violation (AV) error.  Also, nothing was shown on the contact
list, it was all grey.  I then exited the &rq, so had 5 or 7 additional AVs.




Edited by - joxy on 04/16/2002  17:05:11

59
&RQ / OT: tinyapps.org
« on: April 16, 2002, 07:22:57 AM »
i posted my little review of notepadex, metapad and np086 at http://hulumumba.by.ru/notepad-replacements-review.html



Edited by - joxy on 04/16/2002  14:39:54

60
&RQ / Bugs
« on: April 16, 2002, 04:21:49 AM »
0 8 4 3

bug1: when the chat window is closed, and the incoming msg makes is to pop up, and "focus on chat window popup" preference is off, then chat window becomes focused.

when chat window is already open, it does not get a focus on incoming msgs, so this bug does not trigger.  but when the window is closed,  it becomes focused.  i think it shouldn't.

bug2: "open all groups" and "close all groups" items in a contact list context menu cause an access violation error.

Edited by - joxy on 04/16/2002  15:25:05

Pages: 1 2 3 4 5 6