wouldn't a customizable quickscreen a step towards customizable
buttons and menus, which we don't want (or at least didn't want in the
past)? Users will start to question why they can customize the
quickscreen but not the menus. By adding a customizable quickscreen we
will make our arguments
On Mon, Oct 27, 2008 at 2:27 PM, alex wallis
[EMAIL PROTECTED] wrote:
Hi. I'm afraid that this will probably look like i'm complaining hear.
However, again as i've said before in other posts on other topics, with your
above comment, if we have settings as a plugin, we run into the good old
Better default settings:
Backlight timeout is 5s at the moment. Increasing this to 10s would be
better so that new users have enough time to look at the (unfamiliar)
screen.
I think Repeat should be off. I always set Auto Change Directory and
then I am wondering why it isn't working.
--
Rincewind
2008/3/19, Dominik Wenger [EMAIL PROTECTED]:
I think for this Weekly, public reports a Forum section would be nice.
As this concentrates all reports from our Students, is nicely accessible
and allows to easily trace the development of the students.
Of course this should be accompanied
why git? While git has its strong parts I don't think we should try to
get the students use git. Some people feel quite uncomfortable with
the way git works. As long as the repository is public and the
software is OSS I really don't see a reason why we should limit the
student. IMO it
On 12/12/07, alex wallis [EMAIL PROTECTED] wrote:
My question is this once i've found a patch i want to apply how exactly do i
save it to my computer in order that i can apply it later?
i no i must be doing something wrong. as i found several patches i wanted to
apply to rockbox, so what i did
On 11/21/07, RaeNye [EMAIL PROTECTED] wrote:
I would like to know what tools are experienced people using
for developing... like debug, quick transfer code do device, etc...
Can't really call myself exprienced, but I have three advices for you.
1.
I really recommend working with git or
3) make it a fully customizable menu
Jonathan, if I remember this correctly, you already coded something
like this when you introduced the new menu system. So technically it
is possible.
This menu would be configured with a config file that gives pointers
to the main menu entries that should
On 10/8/07, Jonathan Gordon [EMAIL PROTECTED] wrote:
2) there arnt that many settings which it would make sense to add to
the screen so why bother adding it at all?
It would make a few settings / screens easily accessible. These are
the things I would put in a customisable quickmenu:
- view
On 10/8/07, Paul Louden [EMAIL PROTECTED] wrote:
with the full customisable quickmenu, a 'user folder' can be
The difference is: A single user folder will require an incredibly
minimal code change even compared to the probably relatively small
amount that customizable menus require.
If a
] wrote:
On 7/24/07, Simon M. [EMAIL PROTECTED] wrote:
What is unix and is it accessible for the blind?
you can use Emacsspeak (this is an extension to the standard unix editor
emacs != unix ...
(emacs even runs on windows, while unix (naturally) doesn't)
- Dominik
What is unix and is it accessible for the blind?
you can use Emacsspeak (this is an extension to the standard unix editor
Emacs) as an editor and operating system that is completely accessible for
the blind.
http://www.cs.cornell.edu/Info/People/raman/emacspeak/emacspeak.html
--
Rincewind
well, the answers that we gave you about unix are true for linux, too.
On 7/24/07, Tyler Wood [EMAIL PROTECTED] wrote:
Ack!
Ok, stupid me!
I meant, what is linux? and is it accessible to the blind? I'd love to
program for rockbox if I knew what I was doing. I'm stil reading the c
tutorial.
My brother recently got a Sansa and I put Rockbox on it for him this weekend.
There are some different things that I find inconsistent with other
targets, but it is not a bad choice of use for the buttons. I expected
the context menu on a long press of Select, too. But the Sansa has a
second menu
I wrote a patch that adds a scaling factor to the estimated runtime.
With this patch it is possible for users to set the maximum runtime
they get based on experience. This value is then taken to adjust the
runtime display in the info screen and the wps tag (and everywhere
else the function might
I like the runtime display in WPS a lot. I don't think it should be
removed. It wouldn't reduce code size on the relavant targets, being
essential for the archos.
Even if the runtime is not very accurate, it gives me a feeling about
how much time is left in the worst case.
This feature has been
I don't know how the battery percentage and the runtime estimate are
coupled code wise.
If it is not a simple conversion, where the calculations for
percentages and runtimes (which are percentages of the max runtime)
are based on the same algorithm, then it would make sense to me to
keep the more
The problem I see with this:
Themes are special for each player, so we would have an extras
package for every player, not one package for all, like it is now.
And a nicer default theme is a must, because people who want to check
out Rockbox are (normally) not willing to install extras just to
You're right about that, but I think that would be a rather small penalty for
running your own wps like this. Also, a TSR can't do anything with the GUI so
it would take some new trick if that's desired.
Then I hope very much that it is never considered to move existing wps
functionality to a
Is it possible to have settings that need to be saved every shut down
saved in eeprom (i think this is what you call non-volatile settings)?
I'm not asking if it is possible with this patch, only if the
architecture of the new settings system allows intelligent saving of
settings to eeprom in the
now, the #4 option that will be used is
UP/DOWN selects items
LEFT exits no change
RIGHT applies and exits
NAVI (a.k.a. select) makes change but does not exit dir
OFF exits, cancels any changes
OK, I can live with that. I can see that RIGHT to apply makes sense, too.
Could you please say again what #4 really means? I find it quite
confusing to read all the messages again and trying to determine which
#4 you mean.
If it is what I think it is, my objection (or propsition) would be to have
LEFT apply setting and leave screen
STOP/OFF cancel setting
SELECT
On 11/3/06, Michael Sevakis [EMAIL PROTECTED] wrote:
I had a feeling it might be that but don't like to jump to conclusions w/o
invesitgating. So the only one with a nice reset/reboot is the H120?
Just a note: my H120 shuts down on reset, too. No reboot.
I have the newest bootloader (with
As I said in the forums, I vote for something like #4 + #3 + #1
LEFT and RIGHT apply setting wherever the current selection is, unless
a setting was already applied with SELECT, and leave the screen.
STOP leaves the screen and doesn't apply a setting.
SELECT applies the setting where the cursor
A different suggestion, might be better on a different thread:
What about having a pop-up help screen displayed (e.g., after long SELECT)
with a textual description of the setting?
The text itself could come from the language file or from the manual;
There'll be an option not to display this
On 9/26/06, XavierGr [EMAIL PROTECTED] wrote:
Strangely though, I prefer the previous behaviour.
LEFT/RIGHT Applies
STOP cancels.
Currently it is very annoying to see a splash message Canceled each time I
press left on a setting menu. I expect that LEFT will apply my change
because I just want
On 8/24/06, Jonathan Gordon [EMAIL PROTECTED] wrote:
Im 99% sure that the core devs despise (sp?) the idea of users being
able customize the menu order at will...
I am thinking of a way to allow users to add any avilable option to a
special user menu (I tihnk this will be very easy after the
On 8/23/06, Matthias Mohr [EMAIL PROTECTED] wrote:
NOOO!
you all convinced me that this really is a bad idea.
I agree with completely with XavierGr, rockbox menus are great as they
are and don't need a complete rework.
A few settings that you only set once (beep volume, anti skip buffer,
battery...) should be put further down,. Other options, that toggle
functions, for instance crossfade, eq, replaygain,
On 8/23/06, Jonathan Gordon [EMAIL PROTECTED] wrote:
Oh, the text file is not needed... I was just testing you all :D
But I liked the idea with the text file...
this could be made into a wms file - while menu screen :-)
On 8/23/06, Paul Louden [EMAIL PROTECTED] wrote:
I think most things you've mentioned as possibly going in a quick settings
menu actually fit better in the Context Menu (and in fact several of them
already are).
you're right, but i don't know why, but i find the context menu harder
to reach
There are a few things I like about the new button definition for
horizontal scrolling in lists but there are some things that I don't
like, because it makes navigation clumsier for me.
What I like:
It isn't a key combo anymore, so I might actually use it regularily
But what I don't like:
- It
2) I would like to be able to access the 'View current playlist' more easily,
to shift around songs. A long press on the 'On' button is still available,
and seems logic. Unless I'm the only one editing the playlist regularly, I'd
like this implemented.
I made a patch for the Irivers which
I think a patch-forum would be a good idea too, because on Flyspray
patches can easily get out of sight if you don't subscribe to them. In
a patch forum you could follow updates to patches and general
discussion on a patch more easily (for instance you can see which
patches are still activly
Hello,I have a few questions about the button code in gwps.cOn some button definitions in this code this is used, on some not:FOR_NB_SCREENS(i)
gui_wps[i].display-stop_scroll();when do I have to call stop_srcoll in my own button code and can it do harm to call it for every actions I program for my
On 6/18/06, Manuel Dejonghe [EMAIL PROTECTED] wrote:
On 6/18/06, Simon M. [EMAIL PROTECTED] wrote: Another thing, on Line 349 is this code: #ifdef WPS_RC_PAUSE case WPS_RC_PAUSE:
if (global_settings.party_mode) break; This would mean that it isn't possible to pause with the remote when in party
Thanks for all the help you are trying to give me.
You might try setting your vmware to use NAT rather than bridged
networking. Then allow the vmware NAT application (which runs on teh
host) full access to the internet.
Maybe I should try this. On the other hand, I like it the way it is
Recently I made a small patch for myself to have playlist viewer with
REC from WPS. If someone is interested, I can upload it to the Tracker
or mail it.
so I suggest STOP to go from fileview (or tag view) to playlist view and
back.
sounds reasonable to me. Rockbox shouldn't leave buttons
Hello,
I'm using cvs under windows which converts every file to CR-LF style
when I check out. For some reason, apps/plugins/mp3_encoder.c has
CR-LF line endings in the repository which gives me two CR on every
line for this file. This is too much for the compiler.
Maybe a developer with
Daniel Stenberg wrote:
It indicates your CVS client is weird.
I know. It is the native Win32 version which coverts the LFs to CR LF
automatically (and there is no way to stop this).
This is a real problem with my VMWare-Dev-Platform but I solve it by
converting configure and buildzip.pl
2006/5/10, Paul Louden [EMAIL PROTECTED]:
Why not have the dailies done as fullzip?
Personally, I would like to have the dailies with reduced size because
of my ISDN-Connection. The Font-Package is the same for every Build,
so it can be made available at the daily page once as an extra.
General Settings - Playback - Gather Runtime Data
(experimental)
which probably shouldnt be there any more.
Yes, some items need to be cleaned up before release.
Regards, Jens
I would suggest to put the Tagcache and dircache options together. For
instance in system/caching
When
It would be cool to have another crossfade-option:
Only use Crossfade when the next track is NOT from the same artist and album.
This way you can have nice fadings when you create custom playlists
and have gapless when listening to a whole album.
So when you're working at the crossfade options
Hi,
I think the new volume setting is fine and the -db setting is very
intuitive when you get used to it. But I think it wasn't a good idea
to remove clipping prevention completely. The argument was: almost no
hifi-equipment uses clipping prevention, so why should we use it?
Rockbox is better
44 matches
Mail list logo
