• frame.js scrollbars

    From Nightfox@VERT/DIGDIST to All on Mon Nov 23 20:54:54 2015
    I've recently wanted to be able to display ANSI content with a scrollableãinterface, and tonight I found frame.js, which seems to do the job. I startedãusing frame.js a bit tonight to see what it can do. I saw that it has aã'scrollbars' property, but it seems that even when I set it to true, it isn'tãdisplaying scrollbars. I tried making sure v_scroll and h_scroll are bothãtrue, but it still wasn't displaying scrollbars. Is that a known issue? Also,ãwould it display a vertical scrollbar if v_scroll is true and h_scroll isãfalse?ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã
  • From echicken@VERT/ECBBS to Nightfox on Tue Nov 24 08:25:30 2015
    Re: frame.js scrollbarsã By: Nightfox to All on Mon Nov 23 2015 20:54:54ãã Ni> started using frame.js a bit tonight to see what it can do. I saw that itã Ni> has a 'scrollbars' property, but it seems that even when I set it to true,ã Ni> it isn't displaying scrollbars. I tried making sure v_scroll and h_scrollããThose properties are placeholders and don't do much of anything at the moment.ããYou can use the ScrollBar object from scrollbar.js (note the camelCase - thereãis also a Scrollbar object in that same file, which is not Frame compatible) toãadd scrollbars to frames. See comments at the top of the file for options andãinstructions.ããWe'll see about bringing this into frame.js and making those placeholderãproperties actually do something. For now, just attach a ScrollBar to a Frameãprior to calling Frame.open(), and call .cycle() on your ScrollBar as often asãyou call .cycle() on the Frame.ãã---ãechickenãelectronic chicken bbs - bbs.electronicchicken.com - 416-273-7230ã þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.comã
  • From Nightfox@VERT/DIGDIST to echicken on Tue Nov 24 15:19:17 2015
    Re: frame.js scrollbarsã By: echicken to Nightfox on Tue Nov 24 2015 08:25:30ãã Ni>> started using frame.js a bit tonight to see what it can do. I sawã Ni>> that it has a 'scrollbars' property, but it seems that even when Iã Ni>> set it to true, it isn't displaying scrollbars. I tried making sureã Ni>> v_scroll and h_scroll ãã ec> Those properties are placeholders and don't do much of anything at theã ec> moment. ãã ec> You can use the ScrollBar object from scrollbar.js (note the camelCase -ã ec> there is also a Scrollbar object in that same file, which is not Frameã ec> compatible) to add scrollbars to frames. See comments at the top of theã ec> file for options and instructions.ãã ec> properties actually do something. For now, just attach a ScrollBar to aã ec> Frame prior to calling Frame.open(), and call .cycle() on your ScrollBarã ec> as often as you call .cycle() on the Frame.ããThanks.ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã
  • From Nightfox@VERT/DIGDIST to echicken on Wed Nov 25 10:51:24 2015
    Re: frame.js scrollbarsã By: echicken to Nightfox on Tue Nov 24 2015 08:25:30ãã ec> You can use the ScrollBar object from scrollbar.js (note the camelCase -ã ec> there is also a Scrollbar object in that same file, which is not Frameã ec> compatible) to add scrollbars to frames. See comments at the top of theã ec> file for options and instructions.ããI have set up a ScrollBar object with a Frame in my message reader script forãdisplaying messages with ANSI content. It looks like it's working, but I'veãnoticed a couple possible issues with it:ã- When first displaying the file, it looks like the scrollbar has "holes" inãit. This is a screenshot I made as an example (using white as the scrollbarãforeground and light grey as the scrollbar background):ãhttp://bit.ly/1Ndbr0Gã- I have an input loop in my script that waits for a keypress and scrolls theãFrame when the user presses the up or down arrow, PageUp, PageDown, Home, orãEnd. The scrollbar refreshes when I scroll up & down one line (using theãFrame's scroll() method), but after using the Frame's scrollTo() method (whichãI'm using for PageUp, PageDown, Home, and End), the scrollbar doesn't refreshãuntil cycle() is called a 2nd time (which happens when I press PageUp,ãPageDown, Home, or End in my script).ããFor the 2nd issue, I'm not sure if it's something I'm doing wrong in my scriptãor if it's an issue in the scrollbar/frame class.ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã
  • From Nightfox@VERT/DIGDIST to echicken on Wed Nov 25 11:29:03 2015
    Re: frame.js scrollbarsã By: echicken to Nightfox on Tue Nov 24 2015 08:25:30ããHi echicken,ããAnother thing I've noticed about using frame.js to display ANSI content is thatãit doesn't seem to totally refresh the background text when scrolling the ANSIãup & down - Some text from some of the lines is left over when scrolling. Forãexample, in the following screenshots, the ")" in the origin line at the bottomãis left over when scrolling the message down (as the message text moves up):ãhttp://bit.ly/1Ntklt5ãhttp://bit.ly/1Ndg5Mjãhttp://bit.ly/1Ib9YI5ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã
  • From echicken@VERT/ECBBS to Nightfox on Wed Nov 25 15:32:39 2015
    - When first displaying the file, it looks like the scrollbar has "holes" in it. This is a screenshot I made as an example (using white as the scrollbar foreground and light grey as the scrollbar background):

    Not sure. Are you setting the background colour to LIGHTGRAY or BG_LIGHTGRAY? Is the ANSI content being loaded before or after the scrollbar is opened / cycled for the first time?

    - I have an input loop in my script that waits for a keypress and scrolls the Frame when the user presses the up or down arrow, PageUp, PageDown, Home, or End. The scrollbar refreshes when I scroll up & down one line (using the Frame's scroll() method), but after using the Frame's scrollTo() method (which I'm using for PageUp, PageDown, Home, and End), the scrollbar doesn't refresh until cycle() is called a 2nd time (which happens when I press PageUp, PageDown, Home, or End in my script).

    The ScrollBar doesn't actually redraw itself when you call .cycle() on it; it just updates its position info. The drawing takes place when .cycle() is called on the parent Frame. You could try calling .cycle() on the ScrollBar after you have called Frame.scrollTo() but prior to calling Frame.cycle(). (That may or may not help, but it's worth a shot.)

    For the 2nd issue, I'm not sure if it's something I'm doing wrong in my script or if it's an issue in the scrollbar/frame class.

    Probably just differences in the way you're using it and the way I expected to use it. In my input loops, I usually use console.inkey rather than console.getkey, and call [whatever].cycle() each time through the loop. This way, stuff gets updated as needed whether the user has pressed a key or not. (Useful if you want to update stuff in the terminal while the user is idling, etc.)

    ---
    echicken
    electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230ãã---ã þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.comã
  • From Nightfox@VERT/DIGDIST to echicken on Wed Nov 25 15:44:17 2015
    Re: frame.js scrollbarsã By: echicken to Nightfox on Wed Nov 25 2015 15:32:39ãã >> - When first displaying the file, it looks like the scrollbar hasã >> "holes" in it. This is a screenshot I made as an example (using whiteã >> as the scrollbar foreground and light grey as the scrollbarã >> background): ãã ec> Not sure. Are you setting the background colour to LIGHTGRAY orã ec> BG_LIGHTGRAY? Is the ANSI content being loaded before or after theã ec> scrollbar is opened / cycled for the first time?ããI was using LIGHTGRAY. I tried BG_LIGHTGRAY just now, and I think it actuallyãlooks/behaves better with LIGHTGRAY.ãThe ANSI content is being loaded before the scrollbar & frame are opened forãthe first time. Should it be loaded after?ãã >> - I have an input loop in my script that waits for a keypress andã >> scrolls the Frame when the user presses the up or down arrow, PageUp,ã >> PageDown, Home, or End. The scrollbar refreshes when I scroll up &ã >> down one line (using the Frame's scroll() method), but after using theã >> Frame's scrollTo() method (which I'm using for PageUp, PageDown, Home,ã >> and End), the scrollbar doesn't refresh until cycle() is called a 2ndã >> time (which happens when I press PageUp, PageDown, Home, or End in myã >> script). ãã ec> The ScrollBar doesn't actually redraw itself when you call .cycle() on it;ã ec> it just updates its position info. The drawing takes place when .cycle()ã ec> is called on the parent Frame. You could try calling .cycle() on theã ec> ScrollBar after you have called Frame.scrollTo() but prior to callingã ec> Frame.cycle(). (That may or may not help, but it's worth a shot.)ããAh, that seems to help. So it seems that the documentation (comments) inãscrollbar.js are wrong - There's a section of the comments that has an exampleãof how to use it, and it has this:ãif(f.cycle()) {ã s.cycle();ã console.gotoxy(console.screen_columns, console.screen_rows);ã}ãThat seems to suggest that if the frame cycle succeeds, then cycle theãscrollbar. But as you suggested, it seems to work better when the scrollbar'sãcycle() is called before the frame's cycle().ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã
  • From echicken@VERT/ECBBS to Nightfox on Wed Nov 25 22:56:55 2015
    I was using LIGHTGRAY. I tried BG_LIGHTGRAY just now, and I think it actually looks/behaves better with LIGHTGRAY.

    Only the BG_* values in sbbsdefs.js should be used for background colours; using the others may result in strange-looking things.

    LIGHTGRAY incidentally looks better as a background here because - since WHITE is your foreground - it's like not setting a background colour at all. The foreground and background colours are OR-ed together to make an attribute number. In this case you end up with WHITE|LIGHTGRAY, which is 15|7, which is 15, which is WHITE. (You should see the same result when using any other non-BG_* colour as your background, so long as WHITE is your foreground.)

    The ANSI content is being loaded before the scrollbar & frame are opened for the first time. Should it be loaded after?

    Not sure - I was just curious. How are you loading the ANSI stuff into the Frame - using Frame.load(), or some other way (Frame.putmsg(), etc.)?

    Ah, that seems to help. So it seems that the documentation (comments) in scrollbar.js are wrong -

    Not really. The example works, but there's a crucial difference between it and what you're doing. (Which isn't to say that your way is wrong.)

    if(f.cycle()) {
    s.cycle();
    console.gotoxy(console.screen_columns, console.screen_rows);
    }
    That seems to suggest that if the frame cycle succeeds, then cycle the scrollbar. But as you suggested, it seems to work better when the scrollbar's cycle() is called before the frame's cycle().

    Frame.cycle() returns true if something changed, false otherwise. In my example, I'm only updating the ScrollBar if something changed in the Frame it's attached to. However changes to the ScrollBar's position won't be displayed until the Frame is cycled again. In my example, that next Frame.cycle() happens right away. In your code, there's presumably a blocking input prompt (console.getkey perhaps) in between.

    The best solution would be for me to just bring ScrollBar into frame.js, and tie it into the Frame.cycle() method. Then you would use those currently-placeholder properties of Frame to enable scrollbars, and the rest would work behind the scenes - no need to manage the scrollbars separately.

    ---
    echicken
    electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230ãã---ã þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.comã
  • From Nightfox@VERT/DIGDIST to echicken on Wed Nov 25 20:38:35 2015
    Re: frame.js scrollbarsã By: echicken to Nightfox on Wed Nov 25 2015 22:56:55ãã >> I was using LIGHTGRAY. I tried BG_LIGHTGRAY just now, and I think itã >> actually looks/behaves better with LIGHTGRAY.ãã ec> Only the BG_* values in sbbsdefs.js should be used for background colours;ã ec> using the others may result in strange-looking things.ãã ec> LIGHTGRAY incidentally looks better as a background here because - sinceã ec> WHITE is your foreground - it's like not setting a background colour atã ec> all. The foreground and background colours are OR-ed together to make anã ec> attribute number. In this case you end up with WHITE|LIGHTGRAY, which isã ec> 15|7, which is 15, which is WHITE. (You should see the same result whenã ec> using any other non-BG_* colour as your background, so long as WHITE isã ec> your foreground.) ããAh, I see. Perhaps I'll end up changing my script a bit to make things moreãthe way they're supposed to be then.ãã >> The ANSI content is being loaded before the scrollbar & frame areã >> opened for the first time. Should it be loaded after?ãã ec> Not sure - I was just curious. How are you loading the ANSI stuff into theã ec> Frame - using Frame.load(), or some other way (Frame.putmsg(), etc.)?ããI'm using Frame.load() to load an ANSI file.ãã >> Ah, that seems to help. So it seems that the documentation (comments)ã >> in scrollbar.js are wrong - ãã ec> Not really. The example works, but there's a crucial difference between itã ec> and what you're doing. (Which isn't to say that your way is wrong.)ãã >> if(f.cycle()) {ã >> s.cycle();ã >> console.gotoxy(console.screen_columns, console.screen_rows);ã >> }ã >> That seems to suggest that if the frame cycle succeeds, then cycle theã >> scrollbar. But as you suggested, it seems to work better when theã >> scrollbar's cycle() is called before the frame's cycle().ãã ec> Frame.cycle() returns true if something changed, false otherwise. In myã ec> example, I'm only updating the ScrollBar if something changed in the Frameã ec> it's attached to. However changes to the ScrollBar's position won't beã ec> displayed until the Frame is cycled again. In my example, that nextã ec> Frame.cycle() happens right away. In your code, there's presumably aã ec> blocking input prompt (console.getkey perhaps) in between.ããAh, I see. I suppose that is a little different from what I am doing.ãã ec> The best solution would be for me to just bring ScrollBar into frame.js,ã ec> and tie it into the Frame.cycle() method. Then you would use thoseã ec> currently-placeholder properties of Frame to enable scrollbars, and theã ec> rest would work behind the scenes - no need to manage the scrollbarsã ec> separately. ããWould that break existing scripts that are currently managing them separately?ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã
  • From Nightfox@VERT/DIGDIST to echicken on Wed Nov 25 20:40:51 2015
    Re: frame.js scrollbarsã By: Nightfox to echicken on Wed Nov 25 2015 11:29:03ãã Ni> Another thing I've noticed about using frame.js to display ANSI content isã Ni> that it doesn't seem to totally refresh the background text when scrollingã Ni> the ANSI up & down - Some text from some of the lines is left over whenã Ni> scrolling. For example, in the following screenshots, the ")" in theã Ni> origin line at the bottom is left over when scrolling the message down (asã Ni> the message text moves up):ã Ni> http://bit.ly/1Ntklt5ã Ni> http://bit.ly/1Ndg5Mjã Ni> http://bit.ly/1Ib9YI5ããIs this something that you think would need to be fixed in my script? I'm notãsure if I would have to clear the frame's area on the screen in my scriptãbefore I do scrolling in order to erase all the previous text so thatãeverything appears correct after scrolling.ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã
  • From echicken@VERT/ECBBS to Nightfox on Thu Nov 26 00:41:45 2015
    Would that break existing scripts that are currently managing them separately?

    What I think I'll do is leave scrollbar.js where it is, and then have frame.js load it. That way any script currently loading scrollbar.js will still have it available. Frame will then create ScrollBar instances if scrollbars are toggled on, and maintain them for you.

    Even if some script is already using scrollbar.js and setting 'scrollbars' to 'true' on a Frame, it probably won't break anything. You'd just end up with two scrollbars, one layered over the other, doing the same thing, with only the topmost one visible.

    ---
    echicken
    electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230ãã---ã þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.comã
  • From Accession@VERT/PHARCYDE to echicken on Thu Nov 26 02:27:04 2015
    Hello echicken,ããOn 26 Nov 15 00:41, echicken wrote to Nightfox:ãã >> Would that break existing scripts that are currently managing them>ã >> separately?What I think I'll do is leave scrollbar.js where it is,ã >> and then have frame.jsload it. That way any script currentlyã >> loading scrollbar.js will still have itavailable. Frame will thenã >> create ScrollBar instances if scrollbars aretoggled on, and maintainã >> them for you.Even if some script is already using scrollbar.js andã >> setting 'scrollbars' to'true' on a Frame, it probably won't breakã >> anything. You'd just end up withtwo scrollbars, one layered overã >> the other, doing the same thing, with only thetopmost oneã >> visible.---echicken electronic chicken bbs -ã >> bbs.electronicchicken.com - 416-273-7230ãã ec> ===ã ec> þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.comã ec> --- SBBSecho 2.27-Linuxã ec> * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)ã ec> (723:1/1)ããJust an FYI, your replies are coming in here all mangled up. I think part of ãwhat you posted is in the above quote, but some of it is NIghtfox's comments.ããRegards,ãNickãã--- GoldED+/LNX 1.1.5-b20150715ã * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (723:1/701)ã þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)ã
  • From echicken@VERT/ECBBS to Accession on Thu Nov 26 10:11:55 2015
    Re: Re: frame.js scrollbarsã By: Accession to echicken on Thu Nov 26 2015 02:27:04ãã Ac> Just an FYI, your replies are coming in here all mangled up. I think partã Ac> of what you posted is in the above quote, but some of it is NIghtfox'sã Ac> comments. ããThanks. Some sort of newline problem that only shows up ... sometimes, forãsome people, apparently. I'll sort it out eventually. :|ãã---ãechickenãelectronic chicken bbs - bbs.electronicchicken.com - 416-273-7230ã þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.comã
  • From echicken@VERT/ECBBS to Nightfox on Thu Nov 26 10:23:56 2015
    Re: frame.js scrollbarsã By: Nightfox to echicken on Wed Nov 25 2015 20:40:51ãã Ni>> Another thing I've noticed about using frame.js to display ANSIã Ni>> content is that it doesn't seem to totally refresh the backgroundã Ni>> text when scrolling the ANSI up & down - Some text from some of theãã Ni> Is this something that you think would need to be fixed in my script? I'mããProbably an issue with Frame itself. As a workaround you might try usingãFrame.invalidate() to force a redraw (on the next .cycle) after the userãscrolls the Frame (but only if they scrolled it - otherwise you'll beãredrawing needlessly.) May or may not make a difference.ããAre you dumping that message body to a temp file in order to use it withãFrame.load()? If so, any chance you could post the file somewhere? I'd likeãto see if I can reproduce the problem and come up with a fix.ãã---ãechickenãelectronic chicken bbs - bbs.electronicchicken.com - 416-273-7230ã þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.comã
  • From Nightfox@VERT/DIGDIST to echicken on Thu Nov 26 12:28:11 2015
    Re: frame.js scrollbarsã By: echicken to Nightfox on Thu Nov 26 2015 10:23:56ãã Ni>>> Another thing I've noticed about using frame.js to display ANSIã Ni>>> content is that it doesn't seem to totally refresh the backgroundã Ni>>> text when scrolling the ANSI up & down - Some text from some of theãã Ni>> Is this something that you think would need to be fixed in myã Ni>> script? I'm ãã ec> Probably an issue with Frame itself. As a workaround you might try usingã ec> Frame.invalidate() to force a redraw (on the next .cycle) after the userã ec> scrolls the Frame (but only if they scrolled it - otherwise you'll beã ec> redrawing needlessly.) May or may not make a difference.ããI've added that, and it seems to work.ãã ec> Are you dumping that message body to a temp file in order to use it withã ec> Frame.load()? If so, any chance you could post the file somewhere? I'dã ec> like to see if I can reproduce the problem and come up with a fix.ããYes, I am saving it to a file and then calling Frame.load(). I've put the fileãhere:ãhttp://www.digitaldistortionbbs.com/miscFilesForDL/tmpMsg.ansããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã
  • From tracker1@VERT/TRNTEST to echicken on Sat Nov 28 17:57:17 2015
    Thanks. Some sort of newline problem that only shows up ... sometimes, forã > some people, apparently. I'll sort it out eventually. :|ããHappens for me via the default synchronet web interface... here's an example.ããhttp://www.roughneckbbs.com/msgs/msg.ssjs?msg_sub=dove-syncjs&message=110ããYou may have to login, and I'll be offline from sunday until late tuesday forãmy ãmove.ã-- ãMichael J. Ryanãtracker1(at)gmail.comã+o Roughneck BBSãã---ã þ Synchronet þ RoughneckBBS - http://www.roughneckbbs.com/ã
  • From echicken@VERT/ECBBS to Accession on Wed Dec 9 17:45:30 2015
    Just an FYI, your replies are coming in here all mangled up. I think part of what you posted is in the above quote, but some of it is NIghtfox's comments.

    Regards,
    Nick

    I'm not sure if this will be any better ...

    ... but I'm spanning this message across multiple ...

    ... lines because it's fun to do. Anyway, pls respond and let me know if this continues to be mangled kthnx.

    ---
    echicken
    electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230ãã---ã þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.comã
  • From Accession@VERT/PHARCYDE to echicken on Wed Dec 9 19:15:16 2015
    Hello echicken,ããOn 09 Dec 15 17:45, echicken wrote to Accession:ãã >> Just an FYI, your replies are coming in here all mangled up. I thinkã >> part of> what you posted is in the above quote, but some of it isã >> NIghtfox's comments.> Regards,> NickI'm not sure if this will be anyã >> better ...... but I'm spanning this message across multiple ......ã >> lines because it's fun to do. Anyway, pls respond and let me knowã >> if thiscontinues to be mangled kthnx.---echicken electronic chickenã >> bbs - bbs.electronicchicken.com - 416-273-7230ããYep, still mangled. kwlcme. :DããRegards,ãNickãã--- GoldED+/LNX 1.1.5-b20151129ã * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (723:1/701)ã þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)ã
  • From echicken@VERT/ECBBS to Accession on Wed Dec 9 22:11:17 2015
    Yep, still mangled. kwlcme. :D


    Grr, what the fuck. I must sort this out.


    ---
    echicken
    electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230ã þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.comã
  • From echicken@VERT/ECBBS to echicken on Wed Dec 9 22:54:46 2015
    Grr, what the fuck. I must sort this out.ãããRelax, angry guy. You might have just fixed it.ããOr maybe not. We'll see.ãã:|ã---ãechicken ãelectronic chicken bbs - bbs.electronicchicken.com - 416-273-7230ã þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.comã
  • From Accession@VERT/PHARCYDE to echicken on Thu Dec 10 17:01:22 2015
    Hello echicken,ããOn 09 Dec 15 22:54, echicken wrote to echicken:ãã >> Grr, what the fuck. I must sort this out.ããã ec> Relax, angry guy. You might have just fixed it.ãã ec> Or maybe not. We'll see.ãã ec> :|ã ec> ---ã ec> echickenã ec> electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230ã ec> þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.comããThat's how it appears here. Looks a helluva lot better!ããRegards,ãNickãã--- GoldED+/LNX 1.1.5-b20151129ã * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (723:1/701)ã þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)ã
  • From echicken@VERT/ECBBS to Accession on Thu Dec 10 22:39:34 2015
    Hello echicken,ãã> On 09 Dec 15 22:54, echicken wrote to echicken:ãã> That's how it appears here. Looks a helluva lot better!ãã> Regards,ã> Nickãã> --- GoldED+/LNX 1.1.5-b20151129ã> * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (723:1/701)ã> â–  Synchronet â–  thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)ãããYay! Thanks for the reply. Glad that's sorted out.ãã---ãechicken ãelectronic chicken bbs - bbs.electronicchicken.com - 416-273-7230ã þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.comã
  • From Deuce@VERT/SYNCNIX to echicken on Mon Dec 14 14:48:09 2015
    Re: Re: frame.js scrollbarsã By: echicken to Accession on Wed Dec 09 2015 05:45 pmãã > > Just an FYI, your replies are coming in here all mangled up. I think partã > > of what you posted is in the above quote, but some of it is NIghtfox'sã > > comments.ã >ã > > Regards,ã > > Nickã >ã > I'm not sure if this will be any better ...ã >ã > ... but I'm spanning this message across multiple ...ã >ã > ... lines because it's fun to do. Anyway, pls respond and let me know ifã > this continues to be mangled kthnx.ããNot mangled here... maybe because I've to the newest, most awesomeestãword_wrap() implementation?ãã---ãhttp://DuckDuckGo.com/ a better search engine that respects your privacy.ãMro is an idiot. Please ignore him, we keep hoping he'll go away.ã þ Synchronet þ My Brand-New BBS (All the cool SysOps run STOCK!)ã
  • From echicken@VERT/ECBBS to Deuce on Mon Dec 14 19:00:09 2015
    Not mangled here... maybe because I've to the newest, most awesomeestã> word_wrap() implementation?ããI had forgotten to run messages through lfexpand() before saving them. :|ãã---ãechicken ãelectronic chicken bbs - bbs.electronicchicken.com - 416-273-7230ã þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.comã