• Support
  • Articles
  • Resources
  • Products
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead

Broadcast command issue in 4.68 - FIXED

Moderator: boris

11 postsPage 1 of 1

boris
Moderator, LogMeTT and TTLEditor developer

Posts:
1597
Joined: Sat Jan 08, 2005 2:52 pm
by boris » Wed Feb 23, 2011 1:17 am
Hi,

I first reported this issue over 2 years ago with version 4.63 (please check ) and I'm still seeing it in 4.68 on Windows XP Professional SP3.

Failure scenario 1
1) Open 4 connections using TeraTerm. These can be 4 connections to the same server, or to different servers.
2) In any of these 4 TeraTerm windows click on "Control"->"Broadcast Command" menu.
3) Broadcast window appears showing the list with 4 lines each representing one open session.
4) Switch off "Realtime mode". My other settings are: History - checked, CR - selected, Enter key - checked. "Send to this process only" - unchecked.
5) Highlight only the 1st line from the list, which means we want to send command only to one window, listed the first (on top) in Broadcast window.
6) Type date in command entry box and click Submit.
Expected result: The "date" commands should be sent only to the first window and only once.
Actual Result: The "date" commands is sent only to the first window but 4 times.


Failure scenario 2
1) Repeat the steps 1 to 4 from failure scenario 1.
2) Highlight the 1st and the 2nd lines from the list, which means we want to send command only to the first 2 windows.
3) Type date in command entry box and click Submit.
Expected result: The "date" commands should be sent once to the 1 window and once to the 2nd window.
Actual Result: The "date" commands is sent once to the 1st window and 3 times to the 2nd window.


Failure scenario 3
1) Repeat the steps 1 to 4 from failure scenario 1.
2) Highlight the first 3 lines from the list, which means we want to send command only to the first 3 windows.
3) Type date in command entry box and click Submit.
Expected result: The "date" commands should be sent once to the 1st, 2nd and 3rd windows.
Result: The "date" commands is sent once to the 1st and 2nd windows and 2 times to the 3rd window.


Failure scenario 4
1) Repeat the steps 1 to 4 from failure scenario 1.
2) Highlight any line or lines except the 1st line in the list.
3) Type date in command entry box and click Submit.
Expected result: The "date" commands should be sent once to each selected window.
Result: The "date" commands is not sent to any of the windows.


I can easily reproduce each of these failures at any time and wonder if someone else could give it a try and share their experience.
Thanks.
Best regards,
Boris
Yutaka Hirata
TeraTerm Developer

Posts:
606
Joined: Wed Jan 12, 2005 2:35 pm
by Yutaka Hirata » Sun Feb 27, 2011 1:30 pm
Hi Boris,

Thank you for your feedback, and I am sorry for my slow to
fix your problem. I appreciate your greate patience.

I have been fixed your problem and the fix will be included into next release(4.69).

Thanks.
Best regards, Yutaka Hirata
(yutakakn at gmail.com)
http://hp.vector.co.jp/authors/VA013320/
boris
Moderator, LogMeTT and TTLEditor developer

Posts:
1597
Joined: Sat Jan 08, 2005 2:52 pm
by boris » Sun Feb 27, 2011 3:19 pm
Thanks Yutaka!

I thought about this approach, but it has another problem. If each user installs the application in his own directory, upgrading one installation will fail even if another user runs the program from different location.

I think the correct way of solving this issue is to create try-except-end block in install script and inside this block try to rename the file that has to be overwritten and then create a new, temporary file with the same name. If no error, then delete temporary file, restore original file name and continue with the installation. Otherwise, prompt user that there is another instance of the program running on the PC that has to be shut down.
I am planning to write the code for this today and if it works, will post it here.
Thanks.
Best regards,
Boris
boris
Moderator, LogMeTT and TTLEditor developer

Posts:
1597
Joined: Sat Jan 08, 2005 2:52 pm
by boris » Fri Mar 11, 2011 8:53 pm
All failure scenarios from my 1st post in this thread have been fixed in version 4.69. Thanks !!

But I discovered one more for Real Time mode.

Failure scenario
1) Open 4 connections using TeraTerm. These can be 4 connections to the same server, or to different servers.
2) In any of these 4 TeraTerm windows click on "Control"->"Broadcast Command" menu.
3) Broadcast window appears showing the list with 4 lines each representing one open session.
4) Switch on "Realtime mode". All other settings become inactive.
5) Highlight only the 1st line from the list and type date in command entry box. While you type the corresponding command appears in the selected terminal session. Do not click Submit button yet.
6) Highlight other 3 lines in the list and then click Submit.
Expected result: The "date" commands should be sent to the 1st sessions only.
Actual Result: The window that was selected in step 5 above gets "datedate", other windows get "date".

The same happens if 2 or 3 lines are selected in step 5 - two or three selected windows will get "datedate".

I think the correct behavior in Real time mode should be - whatever user types should be send only to the windows that are selected while he is typing and not the windows that were selected later.
Thanks.
Best regards,
Boris
Yutaka Hirata
TeraTerm Developer

Posts:
606
Joined: Wed Jan 12, 2005 2:35 pm
by Yutaka Hirata » Sat Mar 12, 2011 6:19 am
Best regards, Yutaka Hirata
(yutakakn at gmail.com)
http://hp.vector.co.jp/authors/VA013320/
boris
Moderator, LogMeTT and TTLEditor developer

Posts:
1597
Joined: Sat Jan 08, 2005 2:52 pm
by boris » Sat Mar 12, 2011 3:37 pm
Thanks.
Best regards,
Boris
Yutaka Hirata
TeraTerm Developer

Posts:
606
Joined: Wed Jan 12, 2005 2:35 pm
by Yutaka Hirata » Sun Mar 13, 2011 12:12 am
Hi Boris,

At last I understand what you say. Currently when a user presses the submit button,
Tera Term broadcasts the input box data in any mode.
I think that the submit key works the enter key in real time mode.

I will think again this problem.
Best regards, Yutaka Hirata
(yutakakn at gmail.com)
http://hp.vector.co.jp/authors/VA013320/
Yutaka Hirata
TeraTerm Developer

Posts:
606
Joined: Wed Jan 12, 2005 2:35 pm
by Yutaka Hirata » Mon Mar 14, 2011 10:38 am
Hi Boris,

I have uploaded below archive changing the submit button behavior.

http://ttssh2.sourceforge.jp/snapshot/s ... 110314.zip
Best regards, Yutaka Hirata
(yutakakn at gmail.com)
http://hp.vector.co.jp/authors/VA013320/
boris
Moderator, LogMeTT and TTLEditor developer

Posts:
1597
Joined: Sat Jan 08, 2005 2:52 pm
by boris » Mon Mar 14, 2011 1:46 pm
Yutaka,

First of all, on behalf of members and visitors of our site I'd like to express our sympathy and support to all Japanese people affected by recent earthquake and tsunami. I was glad to learn from you that Tera Term project team members and their loved ones are safe. I'm planning to add "How to Help Japan" link on the home page of our web site today.

Now back to the topic of this post:
I tested new version. "Submit" button now works fine, however if you start typing and then uncheck one of the lines, as I described in my last post, then you cannot continue typing. As soon as you return to the entry field, previously entered text becomes selected and when you start typing again it is being erased.

Overall the result text sent to all windows is correct. The only problem now is that right before clicking "Submit" the entry line does not represent what will be actually sent to the open sessions. Also, I think after pressing "Submit" in Real Time mode the entry string should be cleared.
Thanks.
Best regards,
Boris
Yutaka Hirata
TeraTerm Developer

Posts:
606
Joined: Wed Jan 12, 2005 2:35 pm
by Yutaka Hirata » Tue Mar 15, 2011 12:54 pm
Hi Boris,

Thank your your comment. I have updated below archive for your request.

http://ttssh2.sourceforge.jp/snapshot/s ... 110315.zip
Best regards, Yutaka Hirata
(yutakakn at gmail.com)
http://hp.vector.co.jp/authors/VA013320/
boris
Moderator, LogMeTT and TTLEditor developer

Posts:
1597
Joined: Sat Jan 08, 2005 2:52 pm
by boris » Wed Mar 16, 2011 2:43 am
Excellent!! It is working correctly now. Thanks for fixing this!
Thanks.
Best regards,
Boris
Display posts from previous:
Sort by:

11 postsPage 1 of 1

Users browsing this forum: No registered users
cron