BYOND 4.0 Version 430.1005 Release Notes

Fixes

• The layers of controls did not appear correctly or consistently in Dream Maker or Dream Seeker. The controls that came earliest in the tab order should always have appeared beneath controls that came later. Older skins that used overlapping controls may need to be updated if they were designed to exploit the old buggy behavior.


• The 'swap' routine in the icon-editor wasn't respecting the rgb/alpha drawing mode.


• When using an /image with a specific dir as an overlay/underlay, its direction always changed to match the object it was attached to. (Hobnob, SilkWizard)


• Carriage returns were not properly added or removed when sending or receiving text (respectively) through a multi-line input control. (Android Data)


• Panes did not always reset their visibility properly after a reboot or reconnect, creating artifacts like controls appearing in an old spot where they shouldn't appear at all.


• Icons with large numbers of individual frames could increase the number of icons on the client to over 32K, after which further icons would not display correctly. The limit on total individual icon frames available to Dream Seeker has been increased beyond 64K. (Hyarion)


• Clicking an info control's tab just before it disappeared could cause Dream Seeker to crash or freeze. (Jeff8500)


• Tab controls allowed the same pane to be used more than once, which caused Dream Seeker to crash. (JtGibson)


• When the font was changed for the tabs in a tab or info control, the control did not immediately adjust its contents accordingly.


• The layers of controls did not appear correctly or consistently in Dream Maker or Dream Seeker. The controls that came earliest in the tab order should always have appeared beneath controls that came later. Older skins that used overlapping controls may need to be updated if they were designed to exploit the old buggy behavior.


• Focus would switch to the new window/pane after winclone() even if the new window or pane was supposed to be hidden. (Destroy)


• Certain invalid http:// links were crashing DS. (Ghtry)


• Using Shift() to move a non-square big icon north or south without wrap had incorrect results.


• Old overlay/underlay lists were clogging up the server, eventually leaving room for no new ones to be created. (Falacy, SilkWizard, Kakashi24142, others)


• Skins that had their main window's is-maximized parameter set to true did not load their controls with the right position in some cases. This is unlikely to affect any existing skins since is-maximized could not be changed via Dream Maker.


• Alt+numpad key combos were not being recognized as special characters on many systems, and behaved differently on different installations. (DivineTraveller)


• After using Win+L to lock the system or in other similar situations, the map control would stop redrawing until switching to text mode and back (DirectX drawing mode only).


• The label control had some GDI leaks in older versions of Windows (98, ME). These have been reduced, possibly eliminated altogether. (Foomer)


• DS should no longer crash when DX isn't supported (typically in older Win98 installs). Instead it should report a popup alerting the user to the error and fallback on software mode.


• When using max() with a list as the only argument, the max() proc returned null when the list contained only non-positive numbers. There was no similar problem for min(). (Popisfizzy)


• Calling icon() with a nonexistent file could cause Dream Seeker or Dream Daemon to crash. (Alathon)


• Animated icons with a fixed number of loops would base the beginning of their animation on the time the object was first seen by the client, not when the icon or icon state was set. (Popisfizzy)


• A confusing "fmem corruption" error was occurring sometimes when world.cache_lifespan=0 (mainly in DMCGI applications).


• If a verb with a file arg was partially expanded so the command was "Verb '", the parser closed the single quote so the resulting file prompt failed.


• Certain kinds of malformed savefiles could crash the server. (Audeuro)

Features

• Telnet clients now stay alive for much longer periods of inactivity (six hours vs the old value of ten minutes). While we could eliminate the timeout entirely, this prevents phantom clients from building up. DS clients will still timeout after ten minutes, but since they can respond to an internal "ping" message they are much more reliable in detecting true disconnects.


• Windows that have is-pane set to true can use a new parameter, can-scroll, which allows them to show scrollbars instead of resizing to fit their container whenever the container shrinks. (If the container expands to a bigger size than the pane, the pane will still expand with it.)


• can-scroll accepts the values "none" (default), "horizontal", "vertical", and "both". For convenience to developers it also accepts some aliases:
  false -> none
  true -> both
  left, right -> horizontal
  up, down -> vertical


• In the Child control, the new show-splitter parameter can turn the splitter off even if both panes are in use. While off, the splitter can still be moved via winset(), but not by the user since it will not be visible.

  The new lock parameter locks down the size of one of the panes so that if you resize the window, the splitter stays put next to whatever pane you've locked, and the other pane takes the brunt of any size changes. This can be handy if you have something like a map on one side, and don't want the map to shrink or grow every time the user resizes the window.



• In the DM skin editor, the icon-size and text-mode properties of the map control are now available for editing. (Jtgibson)


• Windows/panes no longer flicker so much on resizing. Flicker has also been improved for the Browser, Label, and Button controls. (Foomer)


• It is now possible to set an icon for windows and panes. If you set the icon for your default window, that icon will be used by all other windows by default, including browser popups. If you set an icon for a pane, it will appear if that pane is used in a tab control.


• New feature: winget() now supports a syntax allowing you to get results from multiple controls at once. If you have a window named prefswindow for example and use "prefswindow.*" as the window name, winget() will return the parameters you request for prefswindow and any controls that are immediate children of that window. // Example var/params = winget(usr, "prefswindow.*", "text;is-checked") var/mylist = params2list(params) for(var/item in mylist) usr << "[item] = [mylist[item]]" /* Sample output: prefswindow.message.text = Hi! prefswindow.button1.text = Do you like waffles? prefswindow.button1.is-checked = true prefswindow.button2.text = Do you like SPAM? prefswindow.button2.is-checked = false */ This can also be used for menus and macros. Menus will give you the parameters for every item in the entire menu tree, even sub-menus and sub-sub-menus.

  Separating control IDs with semicolons in winget() can retrieve info about multiple controls at once. // Example var/params = winget(usr, "prefswindow.message;prefswindow.button1", "text;is-checked") var/mylist = params2list(params) for(var/item in mylist) usr << "[item] = [mylist[item]]" /* Sample output: prefswindow.message.text = Hi! prefswindow.button1.text = Do you like waffles? prefswindow.button1.is-checked = true */



• The winset() proc can now be used to change more than one control at once. If the 2nd argument is left null, you can include the control IDs in the parameter list instead: var/list/mylist = list() mylist["mainwindow.input.text-color"] = "#000000" mylist["mainwindow.input.background-color"] = "#ffffff" mylist["mainwindow.output.text-color"] = "#ffffff" mylist["mainwindow.output.background-color"] = "#000000" winset(usr, null, list2params(mylist))


• Windows now have an on-close parameter that can run a command when you close the window, so you can now properly respond to browser popups and other interface windows being closed.


• The Info and Tab controls have an on-tab parameter that runs a command whenever the current tab is changed.


• The output control now has an image parameter which can be used to set a background image. (Due to limitations in Windows, icons/graphics used in your text output will not blend over your background image. Instead they will use the control's background color as a backdrop.)


• All controls now have a font-style parameter that can be used to activate bold, italic, underline, or strikethrough text. A value such as "bold strike" for instance would combine bold and strikethrough styles. For the info control there is a corresponding tab-font-style parameter.


• The input control has a no-command parameter. If set to true, the control behaves as an ordinary text box and does not run commands when you hit Enter.


• History is built separately into each input control, so if you have separate inputs for verbs and chat the two won't get mixed.


• The main control (windows/panes) now has an is-minimized parameter. (Note: This parameter won't save for older skins unless you modify saved-params manually in your skin file, or re-create the window.)


• Fonts included in your .rsc file (by single-quoting the .ttf file in your source code) can be used by clients even if they have not installed that font.


• Interfaces can now use a new Bar control. This control can be either a progress bar or an adjustable slider, straight or an arc.


• New feature: When using the tabs parameter of the tab control, you can precede the value with + to only add tabs without removing any, or - to remove just the tabs you list. // Example // Add scores and tourney panes winset(usr, "mytab.tabs", "+scores_pane,tournament_pane") // Remove chat pane winset(usr, "mytab.tabs", "-chat_pane")


• The new /client/AllowUpload() proc allows you to decide whether to accept a file from a player or not. The two arguments are the filename, and the length in bytes. If you return a true value (the default) from this proc, the upload is allowed. Otherwise, the command or input() that was being used will send back null instead of a file reference.


• Buttons in a skin will no longer activate their commands as soon as they are loaded. The issue that the old behavior was intended to address--making sure "say" or ".alt" showed up in the input control in the default skin--has been solved via an update to the default skin. The new behavior is unlikely to cause any problems, and should make life easier for developers who were unhappy with the old behavior.


• The browser control now responds to changes in its background-color setting. This affects only the outer area with the navigation buttons and such, not the URL bar (if shown) or the document displayed in the browser itself.


• The is-transparent parameter is now implemented for labels. (Most controls still don't use this.) Because of Windows painting issues, transparency has some limitations:
  • Minor flicker will occur when changing visual label settings (such as its text), or the image/color of the window or pane holding the label. This should mostly be noticeable only while resizing.
  • The label will not repaint properly if placed on top of any other control except a Bar control or another transparent label.


• The mouse procs now include an additional "screen-loc" value in the parameters, when available. This only applies when the control involved is the map. The value of this parameter is in the form "[tile_x]:[pixel_x],[tile_y]:[pixel_y]". The tile coordinates correspond to those used by atom.screen_loc, and the pixel coordinates go from 1 (left/bottom) to 32 (right/top). (Alathon)


• The map control now has a new read-only parameter, view-size, which tells the size of the area the map is trying to render. If icon-size is 0, this is the stretched map size minus any "letterboxing". With a specific icon-size, this value can be bigger than the actual map control.


• "as color" is now supported in verbs and input(). This will popup a color selection dialog, returning a #rrggbb string. Example: mob/verb/colorpick() usr << input(usr,"Pick a color, any color","Color","#ff0000") as color


• DM's pixmap editor now shows a running list of colors in use. These can be globally edited by double-clicking, similar to the 3.0 icon-editor.


• DM's pixmap editor's RGB-only and alpha-only modes behave more intelligently now, fully disregarding the alpha (or rgb) components in the displayed image while editing.


• In DM's map editor, ALT+click now makes the topmost object on the current tile active. (Mikau)


• Dynamic resources uploaded to the world's resource cache at runtime can now persist between sessions, consistent with the world.cache_lifespan setting. Note that, as of BYOND 4.0, dynamic resources are stored in a separate cache ([world]_dyn.rsc), so that that the resource cache originally built with the world remains constant. With world.cache_lifespan=0, this dynamic cache is cleared each time the world is run.

429 Release Notes | View All