This is a very marginal issue, and was present in previous Puppies too, but can become annoying:

if for some reason the mouse isn't working, in some instances it's not easy to select menu items from the keyboard (TAB, arrows, space and Enter) since the active item is not always clearly highlighted.

E.g., try changing the screen resolution this way in Dingo's XVesa wizard window: the chosen value can be clearly seen, as a dot appears in the corresponding button, but then neither the <CHANGE> nor the <OK> button get highlighted or focused to show which is the active one, so the job becomes a hit-or-miss game or guesswork (only the script name inside the text box goes in and out of focus by pressing TAB repeatedly).

E.g., try changing the screen resolution this way in Dingo's XVesa wizard window: the chosen value can be clearly seen, as a dot appears in the corresponding button, but then neither the <CHANGE> nor the <OK> button get highlighted or focused to show which is the active one, so the job becomes a hit-or-miss game or guesswork (only the script name inside the text box goes in and out of focus by pressing TAB repeatedly).

Assuming it's a gtk gui you're talking about, then it's a problem with the gtk-theme, so try changing it._________________What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

My point was this: if a total newbie boots Puppy, his mouse doesn't work and he doesn't give up at once, he'll try to play around the main settings from the keyboard; if still more difficulties come out there, he'll most certainly give up Puppy forever.

It's a margin issue, as I said. I quite like the Citrus theme of Dingo, and by far prefer it to the other available GTK themes; but its highlighting ought to be more visible. Most users may care more for this than for having an FTP client or a powerful partitioning tool at hand!

BTW, a review I recently read gave Puppy a big overall thumbs-up, except for a minus to the graphical looks. However silly, this is what gives the very first impression: and an uncertain visual feedback transmits a feeling of insecurity.

I quite like the Citrus theme of Dingo, and by far prefer it to the other available GTK themes; but its highlighting ought to be more visible.

The Citrus theme is pretty bad since it's slow... Try running on old HW and changing between that and a different theme and you'll notice a big difference._________________What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

I'm testing with a K6-II/400; changing from Citrus to any of the other themes I'm unable to detect a quicker response to window opening - maybe my manual test is insufficient: by clicking very quickly twelve times on the "file" (home) icon, with any theme it takes about 0,5 seconds to open the first 2 or 3 windows (about 0,2 sec each), then the subsequent ones open much faster (ten in less than 0,8 sec).

While doing this, I notice that Puppy isn't running entirely from RAM as I expected since this PC has 128MB RAM, the HD has a swap partition and there seem to be 186MB free with SeaMonkey and Geany running.

This happens whether or not I give pfix=ram at boot; I've surely missed something.

I'm testing with a K6-II/400; changing from Citrus to any of the other themes I'm unable to detect a quicker response to window opening - maybe my manual test is insufficient: by clicking very quickly twelve times on the "file" (home) icon, with any theme it takes about 0,5 seconds to open the first 2 or 3 windows (about 0,2 sec each), then the subsequent ones open much faster (ten in less than 0,8 sec).

There isn't much to render in a Rox window (what there is is the mime-types, which are dependent on the Rox-theme, rather than gtk).
Tempestuous mentioned to me a couple of months ago that he's unhappy with Dingo because it's slow, so I tested and found that opening things like Geany is slower with the Citrus theme. It is also noticeable when you shade/unshade windows.

Quote:

While doing this, I notice that Puppy isn't running entirely from RAM as I expected since this PC has 128MB RAM, the HD has a swap partition and there seem to be 186MB free with SeaMonkey and Geany running.

This happens whether or not I give pfix=ram at boot; I've surely missed something.

Since puppy3, the filesystem is only loaded into ram if you have more than 256MB of physical ram._________________What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

While doing this, I notice that Puppy isn't running entirely from RAM as I expected since this PC has 128MB RAM, the HD has a swap partition and there seem to be 186MB free with SeaMonkey and Geany running.

This happens whether or not I give pfix=ram at boot; I've surely missed something.

Since puppy3, the filesystem is only loaded into ram if you have more than 256MB of physical ram.

No, at least No for Dingo, I don't recall about Puppy3, pup_xxx.sfs is copied to ram if there is more than 230000KB (224.6MB) free physical ram. Maybe there are some systems that have 256MB but have less than 224.6MB free at bootup?
Also, Dingo supports 'puppy pfix=noram' to prevent the pup_xxx.sfs from loading into ram._________________http://bkhome.org/news/

No, at least No for Dingo, I don't recall about Puppy3, pup_xxx.sfs is copied to ram if there is more than 230000KB (224.6MB) free physical ram. Maybe there are some systems that have 256MB but have less than 224.6MB free at bootup?

Well, that's kind of nit-picking... Your comment in the script even makes a reference to it being 256MB or above. The point is that when someone with 192MB ram (like me) doesn't get the filesystem in ram (which they used to)._________________What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

No, at least No for Dingo, I don't recall about Puppy3, pup_xxx.sfs is copied to ram if there is more than 230000KB (224.6MB) free physical ram. Maybe there are some systems that have 256MB but have less than 224.6MB free at bootup?

Well, that's kind of nit-picking... Your comment in the script even makes a reference to it being 256MB or above. The point is that when someone with 192MB ram (like me) doesn't get the filesystem in ram (which they used to).

Nitpicking? I only gave a factual reply to your comment:

Quote:

Since puppy3, the filesystem is only loaded into ram if you have more than 256MB of physical ram.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum