I have a Kyro II card and I'm using the powervr drivers ( note : I have
to use mdk 8.2 kernel because the drivers can't compil, even if
everything else is cooker ).
The pb ?
If I just want to change my monitor, XFdrake will override everything
and put fbdev.
So 2 questions :
- does XFrake ignore lines containing # caracters ? I have a look in
Xconfig.pm and can't find the answer :
$c{driver} ||= $1 if /^\s*Driver\s+"(.*?)"/;
- Is there a way to make XFdrake change just the part I want to change ?
i.e I want to change Monitor, only modify Monitor section and ignore
everything else, etc ...
At this time XFdrake act like a wizard but the pb is that it is not very
flexible. XFdrake should have the same layout than drakconnect
3 buttons at the bottom :
______ _________ ________________
| OK | | Custom | | Launch Wizard |
------ --------- ----------------
If the user want to autodetect everything, it will use the wizard :
* Launch Wizard -> Mode Normal/Mode Expert
if Mode Normal then
autodetection -> Set resolution -> Set colordepth -> test -> set to
start at boot -> Write configuration
else
XFree 4.2.0/XFree 3.3.6 -> Set colordepth -> Set resolution -> Propose
to change something else ( Monitor, card, etc ... ) -> If I want to
continue I clik/or select Continue -> test -> set to start at boot ->
Write conf
* The Custom button should display a list that give the choice of what u
want to modify :
Change Monitor
Change Graphic Card
Change Resolution
Change Colordepth
Show Settings
The dialog should have a Apply and Cancel button.
In order not to write a different interface and keep this dialog common
to the one you have when the test fail, if the user select More, this
should set a flag ( like : custom_settings ) and also when he select an
item in the dialog box, there should have a flag set.
So when when you hit Apply, it should check like this :
if custom-settings then
if monitor_change then
change_monitor()
if card_change then
change_card()
if resolution_change then
change_resolution()
if depth_change then
change_colordepth()
# why ? because I may want to change, monitor + resolution at the same
# and don't want to touch card and colordepth
else apply_settings()
apply_settings should be common to Normal/Expert wizard too as it not
going to change settings in an atomic way ( section ) but everything at
the same time and with most of this part coming from autodetection (
depends on the fact you are using expert mode or not ). It grab
everything, even if the user don't have a clue of what have been decided
and make it changes.
Now is coming the problem of show_settings. it seems to show a mix of
settings from the config file and autodetection.
2 possibilities :
+ split the custom part ( show_custom_settings ) and the old part (
show_settings )
+ a flag or an argument.
show settings in custom mode should really only show what have been
defined in config file and what the user have defined
Sorry, I don't know perl, gtk and don't have time to learn and code this
myself. That's why I try to be the most precise as possible in order to
give some ideas
P.S :
My Device section looks like this :
Section "Device"
Identifier "KYRO Series"
VendorName "Unknown"
BoardName "Unknown"
Driver "powervr"
# Driver "fbdev"
# VideoRam 8192
# Clock lines
# Uncomment following option if you see a big white block
# instead of the cursor!
# Option "sw_cursor"
Option "DPMS" "on"
EndSection
