# Toolbar Published articles for Toolbar. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Mikrotik Winbox 4.3 is out DevFeed: [Mikrotik Winbox 4.3 is out]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-29T14:38:07Z Content type: release Language: en Sources: [Justin Wilson (j2sw)]() Topics: [MikroTik](), [Windows](), [Zip](), [GUI](), [layout]() Tags: [2026](), [feature](), [file](), [form](), [input](), [layout](), [mikrotik](), [network-engineering-resources](), [performance](), [redesign](), [render](), [right](), [sorting](), [table](), [toolbar](), [ui](), [v3](), [version](), [widget](), [winbox](), [windows](), [zip]() ### AI overview MikroTik WinBox 4.3 is a release update that adds a Windows ARM64 package and introduces or improves table, form, toolbar, settings, font, login, window-selection, layout, and scrolling behavior. ### Source excerpt What's new in 4.3 (2026-Jul-20 10:14): *) app: add Windows for arm64 version in file WinBox_Windows_arm64.zip;*) form: make multiline input field height logic as in WinBox v3;*) table: add quick comment feature (allow multi-row commenting);*) table: allow opening "Table settings" also via right mouse click;*) table: calculate implicit height to fit 16 regular rows including ... Read more The post Mikrotik Winbox 4.3 is out appeared first on Justin Wilson (j2sw). ## Sketch's Copenhagen update redesigns its macOS Tahoe interface DevFeed: [Sketch's Copenhagen update redesigns its macOS Tahoe interface]() Original publisher: [Read original article]() Author: Freddie Harrison Published: 2025-11-19T06:00:00Z Content type: release Language: en Sources: [Sketch Blog]() Topics: [Sketch](), [macOS](), [ui](), [liquid glass](), [Canvas]() Tags: [features](), [latest-features](), [liquid-glass](), [macos](), [release](), [toolbar](), [ui]() ### AI overview Sketch's Copenhagen update introduces a major redesign for macOS Tahoe, including custom sidebars, sidebar document tabs, subtle Liquid Glass use, and a refreshed layer list with focus mode. ### Source excerpt Our Copenhagen release features an all-new design for macOS Tahoe -- here's how we've balanced a fresh look with functionality. ## What we've learned about designing for accessibility from our users DevFeed: [What we've learned about designing for accessibility from our users]() Original publisher: [Read original article]() Author: lcarmen2 Published: 2023-03-23T16:09:16Z Content type: opinion Language: en Sources: [Slack Design]() Topics: [Accessibility](), [User interface design]() Tags: [accessibility](), [design](), [interface](), [keyboard](), [navigation](), [screen](), [team](), [toolbar](), [what-we-do]() ### AI overview Slack's accessibility team describes changes intended to make Slack easier to navigate for keyboard-only and screen reader users. The article explains how feedback from blind and low-vision users shaped improvements to interface hierarchy, toolbar navigation, focus handling, keyboard navigation, and screen reader announcements. ### Source excerpt Slack's accessibility team recently launched a series of changes to make navigating around Slack more reliable and efficient for keyboard-only and screen reader users. While our accessibility had significantly improved over the last few years, we were still hearing from blind and low-vision users that moving around the interface felt disorienting and noisy. One user [...] The post What we've learned about designing for accessibility from our users appeared first on Slack Design. ## New Property Sheet and JavaDocs DevFeed: [New Property Sheet and JavaDocs]() Original publisher: [Read original article]() Author: Steve Hannah Published: 2022-04-06T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Development](), [Tooling](), [ide](), [debugging]() Tags: [context](), [debugging](), [dependencies](), [development](), [intellij](), [new-features](), [set](), [toolbar]() ### AI overview The article announces a new read-only property sheet, JavaDocs access, property filtering, and a revalidation command in the simulator to improve component inspection and layout debugging. ### Source excerpt We have added a new property sheet and a JavaDocs button to the toolbar of the Properties panel. ## Codename One Simulator Facelift DevFeed: [Codename One Simulator Facelift]() Original publisher: [Read original article]() Author: Steve Hannah Published: 2022-03-18T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [simulator](), [ui](), [Maven](), [configuration](), [monitor](), [Tool]() Tags: [configuration](), [features](), [interface](), [monitor](), [new-features](), [simulator](), [toolbar](), [update](), [updates]() ### AI overview This article describes a Codename One simulator update delivered with Maven 7.0.61. The update consolidates the simulator, component inspector, network monitor, and other tools into one configurable window, with layouts and detached panels remembered between runs. It also moves some simulator controls to a new toolbar. ### Source excerpt With the latest Maven update (7.0.61), you will notice a few changes to the Codename One simulator that should improve your development experience. ## Accessibility of text over generic background color DevFeed: [Accessibility of text over generic background color]() Original publisher: [Read original article]() Published: 2020-03-29T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [Accessibility](), [Application Development](), [Android](), [color](), [User interface design]() Tags: [accessibility](), [accessible](), [android](), [app-development](), [color](), [support](), [toolbar]() ### AI overview This article explains basic accessibility practices for application development, focusing on color contrast between text and backgrounds. It uses an Android companion app for Fibery as a practical example of dynamically coloring a toolbar and choosing suitable text and icon colors. ### Source excerpt Source Introduction One of the important parts of application development is to make it accessible to as many users as possible. This includes people with impaired vision, color blindness, impaired hearing, impaired dexterity, cognitive disabilities, and many other disabilities. Making an app accessible is challenging but rewarding. The difficulty is because the development team should pay attention to some details which often might be overlooked. Though besides some advanced accessibility support might be too expensive to add, there are still some basic best practices to ensure that your app development is heading in the right direction (and can be improved later over time). Basic accessibility support includes providing content descriptions, large enough touchable areas and ensuring good color contrast between foreground and background components. In this article, we'll go in detail on the latest -- color contrast. We'll take a look at one specific situation I faced while developing FiberyUnofficial -- my pet project, Android companion app for https://fibery.io. ## GSoC 2019 - RAPPS DevFeed: [GSoC 2019 - RAPPS]() Original publisher: [Read original article]() Published: 2019-06-11T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Open Source](), [Windows](), [Programming](), [Code]() Tags: [applications](), [c-plus-plus](), [free](), [gsoc](), [open-source](), [os](), [programming](), [project](), [react](), [reactos](), [toolbar](), [win32](), [winapi](), [windows]() ### AI overview A GSoC 2019 progress report describes work on ReactOS's RAPPS software manager. The author added a Download category and download option so multiple software packages can be saved for later installation, with a toolbar shortcut planned. ### Source excerpt Introduction Hello everyone, This is Akshay Patil, 3rd-year B.E CS student from VIIT Pune, lately working on RAPPS. The Google Summer of code, abbreviated as GSoC is an annual program in which Google pairs University Students to work with open source organizations and then awards stipends to students who are able to meet project milestones. This Summer I am working with ReactOS to improve RAPPS. ReactOS is a free and open-sourced operating system based on the Windows NT architecture, providing support for existing applications and drivers, and an alternative to the current dominant consumer operating system. ## Improving graphics interactivity DevFeed: [Improving graphics interactivity]() Original publisher: [Read original article]() Author: Yair Altman Published: 2019-04-21T21:03:10Z Content type: tutorial Language: en Sources: [Undocumented Matlab]() Topics: [MATLAB](), [GUI](), [Usability]() Tags: [graphics](), [gui](), [gui-handle-graphics-medium-risk-of-breaking-in-future-versions-stock-matlab-function](), [handle-graphics](), [medium-risk-of-breaking-in-future-versions](), [performance](), [profiling](), [pure-matlab](), [script](), [stock-matlab-function](), [toolbar](), [usability]() ### AI overview This article examines MATLAB R2018b's default axes mouse interactions, focusing on performance and usability problems. It describes replacing inefficient DataTipInteraction and PanInteraction settings with RegionZoomInteraction and outlines a test setup for measuring the changes. ### Source excerpt Matlab R2018b added default axes mouse interactivity at the expense of performance. Luckily, we can speed-up the default axes. The post Improving graphics interactivity appeared first on Undocumented Matlab. Related posts: Undocumented HG2 graphics events Matlab's new HG2 graphics engine includes many new undocumented events that could be used in various ways. ... Handle Graphics Behavior HG behaviors are an important aspect of Matlab graphics that enable custom control of handle functionality. ... Improving save performance There are many different ways of improving Matlab's standard save function performance. ... Waterloo graphics Waterloo is an open-source library that can significantly improve Matlab GUI. ... ## Dynamic UI with CDK TemplatePortal and DomPortalHost DevFeed: [Dynamic UI with CDK TemplatePortal and DomPortalHost]() Original publisher: [Read original article]() Published: 2018-05-25T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Angular](), [Library](), [ui]() Tags: [angular](), [angular-material](), [demo](), [library](), [mobile](), [toolbar](), [ui]() ### AI overview A tutorial on using Angular CDK TemplatePortal and DomPortalHost to place UI content dynamically between decoupled components. It demonstrates a mobile-like Angular application where routed components provide context-specific page actions in a shared toolbar, without directly coupling the components. ### Source excerpt Lorem ipsum dolor sit amet ## Profiling your Website with Craft CMS 3's Debug Toolbar DevFeed: [Profiling your Website with Craft CMS 3's Debug Toolbar]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2018-04-09T14:09:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [debugging](), [Website](), [Tooling]() Tags: [addition](), [changes](), [cms](), [craft](), [debug](), [debugging](), [helps](), [hood](), [insights](), [performance](), [profile](), [profiling](), [toolbar](), [website](), [websites]() ### AI overview A tutorial on using Craft CMS 3's Debug Toolbar to inspect debugging, performance, and database query information. It explains how to enable the toolbar for the front end or Control Panel and notes that devMode affects the amount of logged information. ### Source excerpt Craft CMS 3 has some big changes under the hood, one of which is the addition of the Debug Toolbar that helps you profile and debug your websites ## New Default Code DevFeed: [New Default Code]() Original publisher: [Read original article]() Author: Shai Almog Published: 2018-03-06T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Boilerplate](), [Code](), [App](), [networking]() Tags: [app](), [code](), [developers](), [error-handling](), [errors](), [event](), [feature](), [github](), [init](), [network](), [networking](), [performance](), [toolbar]() ### AI overview Codename One changed the default boilerplate generated for new hello world apps. The update keeps the code in the init method and adds configurable defaults for two network threads, the global Toolbar, and generic network error handling. ### Source excerpt This is new behavior that went in without fanfare. If you created a new hello world app you might have noticed this. We changed the default boilerplate for Codename One and made it more representative of what you'd want to see in a hello world app. The entire change to the default generated app is within the init method: public void init(Object context) { // use two network threads instead of one updateNetworkThreadCount(2); __**(1)** theme = UIManager.initFirstTheme("/theme"); // Enable Toolbar on all Forms by default Toolbar.setGlobalToolbar(true); // Pro only feature Log.bindCrashProtection(true); addNetworkErrorListener(err -> { __**(2)** // prevent the event from propagating err.consume(); if(err.getError() != null) { Log.e(err.getError()); } Log.sendLogAsync(); Dialog.show("Connection Error", "There was a networking error in the connection to " + err.getConnectionRequest().getUrl(), "OK", null); }); } __1 By default networking in Codename One runs on one network thread for consistency. Two threads make more sense from a performance standpoint. We wanted to make this easily configurable and it should be easy in the init() method __2 Handling network errors in a generic way is probably one of the hardest things to grasp. So many developers are still stuck with the default error handling code... With that in mind we added a bit of boilerplate to handle network errors in a way that makes sense and should be easily customizable I had some thoughts about removing this boilerplate and packaging it in a class. But then I thought again. ## Toolbar Delight DevFeed: [Toolbar Delight]() Original publisher: [Read original article]() Author: Juhani Lehtimäki Published: 2017-09-27T17:06:38Z Content type: tutorial Language: en Sources: [Android UI Patterns - Medium]() Topics: [Android](), [ui](), [Framework](), [implementation]() Tags: [android](), [arc](), [components](), [containers](), [design](), [feature](), [layout](), [toolbar](), [ui](), [ui-framework](), [ux]() ### AI overview This tutorial explains the design and implementation of a custom Android toolbar for the Social Steps app. It covers playful animations and state changes, scrolling behavior with AppBarLayout and CollapsingToolbarLayout, offset tracking, toolbar elevation, and a custom ToolbarArcBackground view. ### Source excerpt In this article we explain how and why we did our Social Steps app custom toolbar from implementation point of view. Design Adding delightful details to your user interface is a great way to push your app above competition (assuming, of course, that all the important functionality exists and is well designed). Toolbar is a playground on Android. We decided to fully utilise it in playful but meaningful animations and state changes. The design for this feature, like for the rest of the Social Steps app, was done by Pierluigi Rufo. Pier has promissed to write about the design side in much more detail soon. Stay tuned! Implementation Android's UI framework is extremely powerful and flexible. If you take the time to learn what you can do with it you'll be adding a very powerful tool to your toolbox. Personally, I believe native Android UI being the most powerful prototyping tool currently available. Nearly everything your designer comes up with you can implement in matter of hours (or at least create an approximation of the intended feature). This flexibility extends to proper, scalable, implementations of production-ready features. In our Social Steps app the toolbar was the obvious place where to push the brand and user delight aspects of the app. To maintain scalability, scrolling containers are very commonplace in Android screens. So much so that Google introduces special components for developers to be able to add interesting and useful behaviour to the Android toolbar: AppBarLayout and CollapsingToolbarLayout. With the two above components and a small custom view it's possible to work magic on your toolbar design. Tracking scrolling eventshttps://medium.com/media/cbcccefeb5031bb6f4e8b840e61f1c66/href AppBarLayout.OnOffsetChangedListener This is the tool you can use to get a handle to events when user scrolls your main view (collapses your toolbar). This code is in my main Activity but it works as well in a Fragment if your toolbar is defined in one. appbarLayout.ad ## GSoC'17 : Project Taskbar Shell Extensions for ReactOS | Final Report DevFeed: [GSoC'17 : Project Taskbar Shell Extensions for ReactOS | Final Report]() Original publisher: [Read original article]() Published: 2017-08-27T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Extension](), [Toolbar](), [win32](), [Windows](), [C++](), [Programming]() Tags: [battery](), [c-plus-plus](), [code](), [extensions](), [free](), [gsoc](), [open-source](), [os](), [programming](), [react](), [reactos](), [toolbar](), [win32](), [winapi]() ### AI overview A 2017 GSoC final report describes work on ReactOS taskbar shell extensions. The project implemented a Quick Launch Toolbar and added notification-area support for battery status and safely removing devices. It also discusses the Win32, COM, and ATL technologies used and the implementation of reusable toolbar-related classes and interfaces. ### Source excerpt Hello, everyone! It's me, Shriraj (a.k.a sr13). The time has come to summarize all the work I have done in this Summer of Code with ReactOS and complete this journey of my first ever GSoC, though my story with ReactOS is just beginning! TL;DR of Project Taskbar Shell Extensions: # Designed & Implemented the Quick Launch Toolbar for ReactOS. # Designed & Added support for Battery Status in notification area (System Tray). ## GSOC Project TSE Week 4 DevFeed: [GSOC Project TSE Week 4]() Original publisher: [Read original article]() Published: 2017-06-29T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [Toolbar](), [browser](), [file](), [navigation](), [Icons](), [ui](), [dialog](), [Shell]() Tags: [browser](), [dialog](), [enumeration](), [file](), [free](), [gsoc](), [icons](), [implement](), [interface](), [navigation](), [open-source](), [os](), [project](), [react](), [reactos](), [toolbar](), [ui](), [win32](), [winapi]() ### AI overview A week-four GSoC progress report describes a working prototype of ReactOS's Quick Launch band. The author implemented shell-folder initialization and enumeration, added folder-browsing UI, displayed file and folder names and icons as buttons, and integrated a context menu with the taskbar menu. ### Source excerpt Hi, everyone!! So you all are still with me? Good!! ;) As I had told last week, that this week will be rather an exciting one, and yes it indeed was. And the reason is, finally, you all will see a working (prototype) of the quick launch band. (yay!!) Let me go through chronologically, what I did this week. The first thing was to Implement the IShellFolderBand. This is a very important interface as it helps to initialize the IShellFolder and PIDL (via its InitializeSFB method) required to enumerate the folder objects. ## Test Recorder and Toolbar DevFeed: [Test Recorder and Toolbar]() Original publisher: [Read original article]() Author: Shai Almog Published: 2017-05-22T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Test-driven development](), [Framework](), [ui](), [Code]() Tags: [code](), [commands](), [features](), [run](), [test](), [tests](), [toolbar](), [ui]() ### AI overview This article explains updates to Codename One's test recorder, including improved handling of toolbar commands and "wait for title" behavior. It also reviews how to record tests, generate assertions, save the test class, and run the resulting tests. ### Source excerpt One of the key takeaways I have from the bootcamp is the need to work on TDD in Codename One. We had a test framework and test recording framework for years, but it wasn't picked up by many developers and as such it stagnated. As we launched the Toolbar API we didn't even check that framework and some basic stuff stopped working. This was something several attendants in the bootcamp mentioned as important as well as a couple of enterprise customers so I knew we had to revisit this feature. With this week's update commands should be handled correctly even with a toolbar and features such as "wait for title" should work for a form with a Toolbar. I'd still recommend using setName() for any component you want to test as this will make the generated code far clearer to the human observer when you record a test. ## Reactive Apps with Model-View-Intent - Part 4: Independent UI Components DevFeed: [Reactive Apps with Model-View-Intent - Part 4: Independent UI Components]() Original publisher: [Read original article]() Author: Hannes Dorfmann Published: 2017-02-25T09:00:00Z Content type: tutorial Language: en Sources: [Hannes Dorfmann]() Topics: [reactive](), [ui](), [App](), [Code]() Tags: [blog](), [design-patterns](), [flow](), [recyclerview](), [shopping](), [toolbar](), [ui-components](), [viewmodel]() ### AI overview This blog post discusses building independent, reusable UI components in reactive application architectures such as Model-View-Intent, Model-View-Presenter, and Model-View-ViewModel. It argues that presenters should communicate indirectly by observing shared business logic and describes this approach using a shopping-basket example. ### Source excerpt In this blog post we will discuss how to build independent UI components and clarify why Parent-Child relations are a code smell in my opinion. Furthermore, we will discuss why I think such relations are needless. One question that arises from time to time with architectural design patterns such as Model-View-Intent, Model-View-Presenter or Model-View-ViewModel is how do Presenters (or ViewModels) communicate with each other? ## Designing ClassPass for Android - touchlab DevFeed: [Designing ClassPass for Android - touchlab]() Original publisher: [Read original article]() Published: 2016-02-19T19:56:55Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Android](), [App](), [Material Design](), [iOS](), [Toolbar]() Tags: [android](), [app](), [architecture](), [bottom-sheet](), [branding](), [case-study](), [design](), [developers](), [discovery](), [featured](), [filter](), [interface](), [ios](), [map](), [material-design](), [search](), [swipe](), [toolbar](), [typography](), [user]() ### AI overview touchlab describes its design work adapting the ClassPass iOS experience for Android while preserving the product's branding and functionality. The article explains a unified map-and-results interface using search, filters, a bottom sheet, and an expandable toolbar. ### Source excerpt In the summer of 2015, touchlab began working with ClassPass, that gives users access to a huge network of fitness facilities for a monthly subscription. ## Android Meetup at WeWork Chelsea Covers Support Design Library and Debugging DevFeed: [Android Meetup at WeWork Chelsea Covers Support Design Library and Debugging]() Original publisher: [Read original article]() Published: 2016-01-21T19:55:38Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Android](), [debugging](), [Toolbar]() Tags: [android](), [community](), [debugging](), [samsung](), [speaker](), [speaking](), [toolbar]() ### AI overview A recap of an Android meetup at WeWork Chelsea featuring talks on the Android Support Design Library and debugging. The event also included practical advice about CollapsingToolbarLayout and discussion of errors, network conditions, and device-specific bugs. ### Source excerpt We kicked off a new year of Android meetups at WeWork Chelsea last Thursday. We're pretty sure we broke some records at the rate that pizza disappeared! ## Use Voice Search to integrate with Google Now DevFeed: [Use Voice Search to integrate with Google Now]() Original publisher: [Read original article]() Published: 2015-10-14T00:00:00Z Content type: tutorial Language: en Sources: [Antonio Leiva]() Topics: [Android](), [Google](), [App](), [Google Search](), [App Indexing]() Tags: [adb](), [android](), [app](), [app-indexing](), [debug](), [google](), [google-search](), [toolbar]() ### AI overview A tutorial on integrating Android apps with Google Now voice search. It explains how to receive the search intent, extract and analyze its query text, update an in-app search interface, and test the integration with adb. ### Source excerpt Everything Android, Kotlin and other random topics ## Design Support Library (IV): Collapsing Toolbar Layout DevFeed: [Design Support Library (IV): Collapsing Toolbar Layout]() Original publisher: [Read original article]() Published: 2015-07-09T00:00:00Z Content type: tutorial Language: en Sources: [Antonio Leiva]() Topics: [Android](), [XML](), [Kotlin]() Tags: [android](), [kotlin](), [layout](), [nested-scroll](), [toolbar](), [xml]() ### AI overview A tutorial on building an Android interface with the Design Support Library's Collapsing Toolbar Layout. It explains how CoordinatorLayout, AppBarLayout, NestedScrollView, parallax behavior, toolbar pinning, and FloatingActionButton anchoring work together in XML, with additional code for toolbar tinting and material transitions. ### Source excerpt Everything Android, Kotlin and other random topics ## Material Design Everywhere: Using AppCompat 21 DevFeed: [Material Design Everywhere: Using AppCompat 21]() Original publisher: [Read original article]() Published: 2014-10-17T00:00:00Z Content type: tutorial Language: en Sources: [Antonio Leiva]() Topics: [Material Design](), [Android]() Tags: [android](), [how-to](), [layout](), [material-design](), [toolbar](), [tutorials]() ### AI overview A tutorial on using AppCompat 21 to add Material Design to Android apps while supporting older API levels. It covers project setup, themes, Lollipop-specific transitions, and replacing the ActionBar with the Toolbar. ### Source excerpt Everything Android, Kotlin and other random topics ## ReactOS toolbar click issue traced to SetCapture mouse tracking DevFeed: [ReactOS toolbar click issue traced to SetCapture mouse tracking]() Original publisher: [Read original article]() Published: 2014-04-15T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [Windows](), [opensource](), [Toolbar](), [Code]() Tags: [code](), [free](), [open-source](), [os](), [react](), [reactos](), [toolbar](), [win32](), [winapi](), [windows]() ### AI overview A ReactOS development update discusses a toolbar click issue. The apparent cause was related to using SetCapture to track mouse movement over the toolbar; disabling that code allowed clicks through but stopped other features from working. ### Source excerpt This week really didn't "start"; it was merely a continuation of the past weeks. The issue where the toolbar did not receive clicks was one of those annoying problems where finding the apparent cause is easy, but finding a solution not so much. The issue, as far as I could tell, was related to using SetCapture as a means to track the mouse movement on top of the toolbar. If I disabled that piece of code, the clicks got through, but - of course - other features stopped working. ## ReactOS RShell DevFeed: [ReactOS RShell]() Original publisher: [Read original article]() Published: 2014-03-10T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [WINE](), [implementation](), [Windows](), [bug]() Tags: [bug](), [free](), [open-source](), [os](), [react](), [reactos](), [testing](), [toolbar](), [win32](), [winapi](), [windows](), [wine]() ### AI overview A ReactOS developer investigates start-menu issues in rshell, including misaligned submenu glyphs, missing menu items, and submenus that fail to open. The investigation links the functional problems to incorrect use of MENUITEMINFO flags and button IDs, while the visual issue is attributed to the replacement Marlett font. ### Source excerpt I began the week by testing the progress of the start menu in ReactOS. You may remember this screenshot from last weekend's report. In it, you can see the results of implementing vertical menus in a different, more documented, way. This method requires more work to be done per item, to make them all wrap into a new row, but it is supported by the Wine toolbar implementation ReactOS uses. ## Look&Feel of the Start Menu DevFeed: [Look&Feel of the Start Menu]() Original publisher: [Read original article]() Published: 2014-03-03T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [GUI](), [Programming](), [Windows]() Tags: [free](), [keyboard](), [open-source](), [os](), [programming](), [react](), [reactos](), [toolbar](), [win32](), [winapi](), [windows]() ### AI overview A ReactOS development update describes improvements to the start menu's appearance, hot-tracking behavior, and keyboard navigation. It also discusses codebase reorganization, investigation of taskbar and browseui functionality, and plans to address explorer-new and start-menu issues. ### Source excerpt This week's work began by improving the look&feel of the start menu so that it matches the Windows start menu better. The first step was to improve the look of the menu: This included positioning, colours, dropdown arrows, icon sizes, etc. I continued by trying to improve the feel of the menu: Hot-tracking behaviours, keyboard navigation, etc. The keyboard navigation keeps resisting me somewhat, though, as it tends to glitch when using the left/right arrow keys to open and close submenus, but moving up and down seems to behave as expected. [Next page]()