Scratchpad Bug

[Limbic~Region]

gods, devils, and the rest of the motley crew,
I just went to my home node, clicked on the "Edit Private" link for my scratch pad and submitted some stuff on it. I then navigated to Newest Nodes and back to my home node and clicked on "View" for my public scratchpad. Guess what - it was my private pad.

From within my pad, clicking on "View Public" is enough to revert to proper behavior but I doubt this is the intended process.

[demerphq]

Scratchpad viewmode is 'sticky' because it made several things managable. Its not ideal, but it does work pretty well.

Anyway, to be clear: if 'viewmode' is not specified when viewing a scratchpad it will display in the last mode explicitly requested. Selectcode to download support (in all forms) from a scratchpad depends on this stickyness.

What was wrong is that a key function, called scratchpad_link was not supplying a default mode. This is fixed now, so there should be no more surprising behaviour, except if people link to your own scratchpad by id. People linking to your pad using [pad://user] will get the correct thing (as it uses scratchpad_link).

[Limbic~Region]

demerphq,
I realize I don't have much room to complain here as I am not a devil nor do I desire to be one. I do however feel I contribute in other meaningful ways. One of which in the past was financially.

I am not sure why the community doesn't have more a say in what features get added or not. I don't really like the changes to the scratchpad, inbox, or a few other things I don't remember at the moment. I also don't remember there being a request for input before implementation either.

I am not suggesting that every change require a consensus vote. The people managing the site have always done a decent job of exercising common sense. It is just frustrating and I am just venting. I am not going anywhere anytime soon but I will no longer contribute money (for reasons explained elsewhere).

Update: I figured I should be fair. There is Inner Scriptorium for discussion on changes to the site. As indicated, it intended to be used by pmdev. Regular users are only made aware of new entries when they appear on Newest Nodes. As pointed out by bart in No link to Scriptorium, there hasn't been a whole lot of announcement about this section or what it is for so how would anyone know to go there looking for proposed ideas. In other words, it is convenient to say that a topic affecting the entire town will be discussed at the next town meeting but doesn't do anyone much good if the announcment is in fine print of the last page of the newspaper

[demerphq]

Seperating the scratchpad private content from the public content was a long standing request/objective/todo. Improving the inbox had a number of objectives and was discussed in the CB and in Scriptorium around the time it was done. There was even a trial version released so people could give feedback. I dont recall you protesting back then.

If you have specific issues with the scratchpad stuff or the inbox then please express them clearly and ill see what I can do. But I think you should remember a lot things that you probably take for granted on the site were coded by me so I think you can give me a break when something I've done doesn't exactly match your preferences.

Regarding the money issue comment I'm not really sure why you want to say it to me. I'm not responsible for how PM money was handled, I never received a cent for any of my contributions and never asked for any. I did ask for some of the PM money to go towards supporting the pmdev server, but since of late I havent had the time (or frankly the inclination) to work on PM much I never really followed up on it as I couldn't guarantee the money would be well used.

[jdporter]

Yes; apparently, from looking at the code, that is the intended behavior of the View link on homenodes.

The viewmode parameter is "sticky"; that is, if passed, it gets remembered in a $VARS entry. Unlike the other three links, the View link on the homenode does not attempt to set this parameter, so the remembered value is used.

There does appear to be some support in place for a non-sticky variant (the showmode parameter); but currently, the homenode links do not use it.

[BrowserUk]

I encountered this too. Along with a couple of other anomolies that I'm sure I see now and again, but can never reproduce.

Like som eof the other recent changes to PM, simplicity has be traded for complexity. Often incorporating modality, which I personally dislike.

I'm a simple soul who can't stand vi because of modality, but lots of people swear by it. I just swear at it :)