Page 1 of 1

URL Prefs oddity

Posted: Fri Apr 10, 2015 9:40 pm
by Raziel
Just a question here as i'm really puzzled now.

I was looking for some hints on how the URL prefs are being configured and why they are configured by default the way they are.
I couldn't find any hints...so i did what i always do, lod the Prefs file into Notepad and skim through the readable text :-)

Look what i found:

Starting from line 30 upto line 84
Hidden Text - Click to Show :
Copyright (C) 1985-2012 Hyperion Entertainment CVBA.Copyright (C) 1985-2012 Hyperion Entertainment CVBA.ScreenMode preferencesLoad ScreenMode preferencesSave ScreenMode preferencesScreen modesMode properties_Width:_Height:_DefaultD_efaultC_olors:_AutoscrollVisible size:Maximum size:Minimum size:Maximum colors:InterlacedRequires ECSSupports genlockDoes not support genlockDraggableNot draggable00000 x 00000%lU x %lU%ld%ld K%ld MThe selected screen mode has not been tested
successfully.
If your monitor cannot display this screen mode,
you won't be able to see anything.
It is strongly recommended to test a screen mode
before using it.Save|Cancel_Use|_Test|_CancelThe test screen could not be opened.

This can be due to insufficient free video memory available;
please try again with a smaller screen size.

You should not use this screen mode with the current settings.Please click [OK] if this screen is displayed properly.
This will mark the screen mode as successfully tested,
otherwise it will be considered as untested.%ld secondsScreenmode screen%ld secondHorizontal frequency:Vertical frequency:Available screen modesWidth of currently selected
screen modeHeight of currently selected
screen modeSet to use built-in default valueMaximum number of colors of the
currently selected screen modeSet this if you want an oversized
screen to scroll automaticallyTest the current screen modeProperties of the currently
selected screen mode_Stop timerRe_start timerModeID:Available ModesMonitors_Detect settings automaticallyManual settings_Add_Edit_RemoveEnable _InterruptsAllow _FakeNative modesRefresh RatesMinimum _VSyncMaximum V_SyncMinimum _HSyncMaximum HS_ync_Save MonitorYou are about to remove an active mode
from the currently used monitor.

This may lead to this mode not being available
next time you restart your computer.

Proceed?_OK|_CancelEdit monitor modeAdd monitor mode_Width_Height_Vertical RefreshMode is _activeType of Reduced Blanking_Confirm ChangesAl_l supported modesMonitors _preferred modeSelect which monitor driver to configure.Let the system query the monitor to determine
all the supported display modes.
This will also determine the supported
refresh rates for this monitor.All monitors have a "Preferred" mode which usually
matches the native resolution of the display device.

Choose between the system only being presented
with the Preferred mode, or all supported modes
of the monitor.

Some modes may be possible at more than one
refresh rate, 60Hz is the basic rate for all monitors.These manually configured mode specifications
are presented to the system by the driver
as supported by the monitor.
Inactive modes are stored but not presented.Enable/disable hardware interrupts for the display
adapter this monitor is connected to.Allow/disallow FakeNative modes to appear
in the available screen mode list.This is the minimum vertical refresh
rate that this monitor supports.This is the maximum vertical refresh
rate that this monitor supports.This is the minimum horizontal refresh
rate that this monitor supports.This is the maximum horizontal refresh
rate that this monitor supports.Edit the currently selected
monitor mode specification.Define a monitor mode specification
and add it to the above list.Remove the currently selected
monitor mode specification.Save the changes to the current monitor.The configuration of the "%s" monitor
driver has been changed and will be lost.

Save monitor now?_Save|_ForgetShow only _60Hz modes.NoneThe changes made to the monitor(s) will take
effect next time you restart your Amiga.Reboot now|IgnoreRe_vert ChangesReset the monitor data back to the last saved settings._DoubleScanURL ScreenURL PreferencesThe clients that are currently configured for this protocol.
Double-click an item to edit the contents.Turn on or off the debugging
mode for this protocol.Add a configured client to this protocol.Remove the selected client from the above list.Reconfigure the selected client in the above list.Move the selected client up in the listMove the selected client down in the listActiveClient NameClient PathCommandline Format_Add new client_Remove client_Edit clientEnable _Debug for this protocolPlease enter a suitable test URLThe changes you have made will be lost if you exit without saving

Do you wish to continue?‚‚‚‚8‚L‚`-‚„‚¬‚Ì‚ä ƒ
ƒƒƒ(ƒ0ƒ8ƒ@ƒHƒPƒXƒ`ƒhƒ|ƒŒƒ˜ƒ€+ƒŽƒÄƒÌ,ƒÔƒÜƒäƒèƒø„ „!„0"„H#„p$„Œ%„€&„ž'„Ø(„ô)…*…0.…ˆ'…À'…Ø'…ô'†'† '†0'†8'†D'<†P'†\'†h'†t'†„'†”'†€'†Ž'†À' †Ð'!†ä'"‡'#‡'$‡'%‡,'&‡8''‡<'(‡D')ƒÔ'*‡L'+ˆ ',ˆ,'-ˆ@'.‰'/‰¬'0‰ž'1‰Ì'2‰Ø'3‰ð'4Š'5Š'6ŠD'7Šp'8Š”'9ŠÔ':‹';‹8'=‹l'>‹x'?‹ˆ'@‹'A‹ 'B‹¬'C‹Ì'D‹Ü'E‹ä'F‹ì'G‹ô'HŒ'IŒ 'JŒ0'KŒ@'LŒP'MŒ`'NŒp'OŒ€'P('Q4'RH'S† 'T\'Ud'Vl'W€'X'Y¬'ZÀ'[Ø'\ô']Ž '^Žž'_ô'`˜'aô'b‘D'c‘Œ'd‘Ô'e’'f’d'g’œ'h’à'i“'j“H'k“¬'l“Œ'm“Ô'n“Ü'o”4'p”H'q”X'r””p”œ”q”š”Ô”ž”Õ• ”Ö•X”ו„”Ø•Ž”Ù•è”Ú–•8–<•9–D•:–P•;–\•œ–p•–€•ž–•Ÿ(–– –d–À–e–ä17.12.2013ENV:Launch-Handler/URL/DefaultsENVARC:Launch-Handler/URL/DefaultsENVARC:Launch-Handler/URLENV:Launch-Handler/URLÿÿ@ÿÿ|žÿÿ~Lÿÿ~Xÿÿ~€ÿÿ~ ÿÿ@ÿÿ~Àÿÿ€Lrequester.classmainSYS:button.gadgetURL:column: %ld
APPDIR:%s"URL=*"edit_this_as_per_tab_name://%s*""copy ENVARC:Launch-Handler/URL ENV:Launch-Handler/URL ALL QUIETÿÿÌ8ÿÿ»$ÿÿŒhÿÿÄÿÿÄ4ÿÿÄXÿÿÄ|ÿÿÈÀÿÿÇžÿÿÊÿÿË<ÿÿÌ(;clientnamedebugclientnameclientpathcmdformat;===========================================================================
;$%s: launch-handler config, created by URL preferences %ld.%ld (%s)
Ok...so what's doing a whole bunch of the Screenmode prefs text in there?

As you can see the URL prefs really only start after line 84.
While i'm pretty sure that the text above isn't used in any way in the URL prefs it still makes me wonder...WHY is it there?
Was URL Prefs recycled from Screenmode Prefs?

BTW: I found the info i was looking for, so mission accomplished :-)
;$%s: launch-handler config, created by URL preferences %ld.%ld (%s)
;===========================================================================
;
;Syntax:
; The directives for each client must occupy the one line.
; Comments begin with ; effective to end of line.
; Keywords are not case sensitive.
; '=' sign is optional.
; Parameters that contain = or spaces must be enclosed within "" quotes.
; At least one space must be present between directives.
; Blank lines are ignored.
;
; See Also; dos.library/ReadLineItem() for additional semantics.
;
;Keywords:
; CLIENTNAME = "CLIENT NAME"
; Name of client to display in requester, if more than one.
;
; CLIENTPATH = "Sys:internet/client"
; AmigaDOS path to the client to be run.
;
; CMDFORMAT = "URL=http://%s"
; The exec RawDoFmt() format string specifier, where the
; token '%s' will be the command string.
; The command string will have the protocol part removed.
;
; DEBUG Specifying this directive will show the formatted
; commandline, just before it is executed.
;
;===========================================================================

Re: URL Prefs oddity

Posted: Fri Apr 10, 2015 9:55 pm
by broadblues
Firstly if you *must* go poking arround in an executable use a binary datatype or some other program that reads the info *READ ONLY* not Notepafe where you could accidentally save over the file and clobber it.

No idea why that random text is in there, but gcc does have bug where it fills areas of executables with random memory.

Don't compile programs at the same time as buying stuff online :-)

What you are looking for may be found in

envarc:launch-handler/URL/

Re: URL Prefs oddity

Posted: Fri Apr 10, 2015 10:13 pm
by Raziel
broadblues wrote:Firstly if you *must* go poking arround in an executable use a binary datatype or some other program that reads the info *READ ONLY* not Notepafe where you could accidentally save over the file and clobber it.
No risk, no fun :-D

Where would you devs be if there wasn't some stupid users who complain about suddenly not working stuff ;-)
No idea why that random text is in there, but gcc does have bug where it fills areas of executables with random memory.

Don't compile programs at the same time as buying stuff online :-)
Ah...first time i hear about that gcc problem...and first day i'm looking forward to the bugfixed (and updated) version ;-)
What you are looking for may be found in

envarc:launch-handler/URL/
Right, thanks a lot