FLOW MASTER
Flow Master
Страницы · Flow Master

Component Management

Components are the building blocks of automation in Flow Master. They represent UI elements that can be recognized and interacted with across different applications.

Table of Contents

What are Components?

Components are screenshots of UI elements (buttons, text fields, icons, etc.) that Flow Master can:

  • Locate on screen using image recognition
  • Interact with through clicks, drags, or text input
  • Monitor for changes or appearance

Each component includes:

  • Image: Screenshot of the UI element
  • Name: Descriptive identifier
  • Type: Button, input field, icon, etc.
  • Match Settings: Threshold and recognition parameters

Capturing Components

Basic Capture Process

  1. Open Target Application

    • Ensure the app with your target UI element is visible
    • Position the element clearly on screen

  2. Start Capture

    • Click "Capture Component" in Flow Master
    • Your screen will be captured for selection

  3. Select Element

    • Drag to select the UI element you want to capture
    • Aim for just the essential part (avoid extra background)

  4. Configure Component

    • Enter a descriptive name
    • Choose component type
    • Adjust matching threshold if needed

  5. Save Component

    • Click "Save" to add to your library

Best Practices for Capture

✅ Good Captures

  • Unique Elements: Capture distinctive UI parts
  • Minimal Background: Include only necessary pixels
  • High Contrast: Elements with clear edges work best
  • Stable Content: Avoid elements that change frequently

❌ Avoid These

  • Generic Elements: Plain buttons without unique text/icons
  • Dynamic Content: Elements that change color/text
  • Small Elements: Tiny icons or text that's hard to distinguish
  • Overlapping Content: Elements partially covered by other UI

Capture Tips by Platform

Windows

  • Use Windows' built-in magnifier for precision
  • Capture at 100% display scaling when possible
  • Avoid capturing window shadows or transparency effects

macOS

  • Use the built-in screenshot tools for practice
  • Consider Retina display scaling in capture
  • Capture in the same display mode you'll run automation

Linux

  • Ensure consistent window manager theming
  • Test captures across different desktop environments
  • Use consistent display scaling settings

Component Types

Button Components

  • Click Actions: Standard left-click interactions
  • Context Menus: Right-click for context menus
  • Double-Click: For items requiring double-click

Input Field Components

  • Text Input: Type text into fields
  • Clear and Type: Clear existing text before typing
  • Append Text: Add to existing content

Icon Components

  • Status Indicators: Monitor for appearance/disappearance
  • Navigation Elements: Menu items, toolbar icons
  • State Changes: Icons that change based on status

Custom Components

  • Drag Sources: Elements to drag from
  • Drop Targets: Areas to drop onto
  • Scroll Areas: Regions for scrolling actions

Managing Your Library

Organization Strategies

Folder Structure

text

Naming Conventions

  • Descriptive Names: "Gmail - Compose Button"
  • App Prefixes: "Chrome - Address Bar"
  • Action Hints: "Submit Form - Blue Button"

Component Maintenance

Regular Reviews

  • Test Components Monthly: Verify they still work
  • Update Changed UI: Recapture when apps update
  • Clean Unused: Remove components no longer needed

Version Management

  • Backup Components: Export library before major changes
  • Tag Versions: Note which app version components work with
  • Update Gradually: Test updated components before replacing

Advanced Techniques

Multiple Matching Strategies

Fuzzy Matching

  • Lower matching thresholds for elements that change slightly
  • Useful for buttons that highlight on hover
  • Test different threshold values (80-95%)

Template Matching

  • Capture multiple variations of the same element
  • Create component groups for different states
  • Use conditional logic to try different variations

Cross-Platform Components

Resolution Independence

  • Capture at multiple screen resolutions
  • Test components on different display scales
  • Use relative positioning when possible

Theme Variations

  • Capture both light and dark theme versions
  • Account for high contrast modes
  • Test with different system fonts

Performance Optimization

Efficient Captures

  • Minimal Size: Capture smallest distinctive area
  • Strategic Placement: Place frequently used components first
  • Smart Grouping: Group related components together

Search Optimization

  • Use descriptive tags for quick filtering
  • Implement smart search with keywords
  • Create favorites for most-used components

Troubleshooting

Component Not Found

Check These First

  1. Visibility: Is the component currently visible on screen?
  2. Position: Has the window moved or resized?
  3. Appearance: Has the UI changed since capture?
  4. Scaling: Is display scaling the same as during capture?

Solutions

  • Recapture: Take a new screenshot if UI has changed
  • Adjust Threshold: Lower matching percentage in settings
  • Multiple Versions: Capture variations for different states
  • Positioning: Use relative positioning instead of absolute

False Positives

When Components Match Wrong Elements

  • Increase Threshold: Require higher matching percentage
  • Refine Capture: Capture more distinctive features
  • Add Context: Include surrounding elements for uniqueness
  • Use Regions: Limit search to specific screen areas

Performance Issues

Slow Component Recognition

  • Optimize Images: Reduce component image sizes
  • Limit Search Area: Define search regions
  • Cache Results: Use component caching for repeated searches
  • Batch Operations: Group multiple component searches

Platform-Specific Issues

Windows

  • DPI Scaling: Ensure consistent scaling settings
  • Windows Updates: Retest after major OS updates
  • Antivirus: Add Flow Master to exclusions

macOS

  • Retina Displays: Account for high-resolution captures
  • Dark Mode: Test components in both light and dark modes
  • Security: Verify accessibility permissions are granted

Linux

  • Window Managers: Test across different desktop environments
  • Themes: Ensure consistent theming for captures
  • Dependencies: Verify all required packages are installed

Component Library Best Practices

Backup and Sync

  • Regular Exports: Export component library weekly
  • Version Control: Keep track of library changes
  • Team Sharing: Share components across team members
  • Cloud Backup: Store backups in cloud storage

Documentation

  • Component Notes: Add descriptions for complex components
  • Usage Examples: Document common use cases
  • Maintenance Log: Track when components were last verified
  • Troubleshooting Notes: Record solutions to common issues

Collaboration

  • Naming Standards: Establish team naming conventions
  • Quality Review: Have components reviewed before sharing
  • Update Notifications: Alert team when components change
  • Shared Libraries: Maintain common component collections