Re: nodesync is changing the cursor color
By: deon to Digital Man on Sat Apr 18 2026 07:33 am
> Re: nodesync is changing the cursor color
> By: Digital Man to deon on Fri Apr 17 2026 01:29 pm
>
> Howdy,
>
> > This is "not the way". You should use Ctrl-A codes (or set
> > console.attributes property) so that:
>
> I guess I dont understand why there "is a way"?
Because Synchronet support multiple terminal types, not just ANSI.
> Nor do I understand why
> nodesync needs to modify the screen back to a state, I would have expected
> that be a task in console.* object if it was required at all?
nodesync() can display stuff to the screen (e.g. node messags/alerts/telegrams),
so it wants to restore the "current" attribute after doing that. Sending a raw
ANSI sequences changes the attribute on the terminal (well, "some" terminals) wi
thout informing Synchronet that's been done.
> The jsobjs.html implies that nodesync will only do something to the terminal
> (clear it), if an argument is given. Why does it need to send something to
> the terminal anyway, no argument is given?
nodesync *can* display the messages I mentioned above in addition to time left,
pending events warnings, etc.
> Does it send the color change everytime its called, even if the resulting
> color change is already the current color being used by the terminal?
No.
> It might be helpful to update that description to include console state,
> since it is doing more than clear the terminal even without an argument.
Okay. The Baja SYNC function does the same thing, so that me helpful too:
https://synchro.net/docs/baja.html
--
digital man (rob)
Sling Blade quote #15:
Doyle Hargraves: What'cha doin' with that lawn mower blade Karl?
Norco, CA WX: 82.0°F, 15.0% humidity, 3 mph WNW wind, 0.00 inches rain/24hrs
---
■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ [vert/cvs/bbs].synchro.net
|
