Author: pw

7 Tips to Customize Matrix Screen Locker for Faster Access and Better Security

1. Use a strong, memorable unlock method

• Choose: PIN or pattern for speed; passphrase for stronger security.
• Tip: If using PIN, pick 6+ digits that you can reliably recall but aren’t easily guessed (avoid birthdays, repeated digits).

2. Enable biometric fallback with secure timeout

• Set: Fingerprint/face unlock for immediate access.
• Configure: Require biometric only when device is unlocked recently; after a longer idle period (e.g., 6–12 hours) require PIN/passphrase to prevent spoofing.

3. Optimize lock-screen shortcuts

• Add frequently used apps (camera, notes, wallet) to the lock screen to reduce unlock steps.
• Limit which apps appear to minimize exposure of sensitive data.

4. Fine-tune timeout and wake behavior

• Shorten auto-lock timeout for security (30–60s) if you’re in public; lengthen (2–5 min) at home for convenience.
• Set “wake to unlock” so a quick tap/power press immediately shows the unlock UI without extra swipes.

5. Configure notification visibility safely

• Show: app name but hide message content on lock screen.
• Use: per-app notification settings so only non-sensitive apps display previews.

6. Use secure boot and tamper protections

• Enable: any available secure-boot, verified boot, or trusted execution settings to detect tampering.
• Turn on: lock-screen protections that prevent USB/ADB access while locked.

7. Regularly update and audit lock settings

• Update: the Matrix Screen Locker app and system software to get security fixes.
• Audit: your unlock methods, shortcuts, and notification settings every few months and after major updates.

If you want, I can expand any tip into step-by-step instructions for Android or Windows (choose one).

Magic Mirror Sync vs. Traditional Mirroring: Which Is Right for You?

What they are

• Magic Mirror Sync: A smart, usually cloud-assisted mirroring system that keeps content, settings, notifications, and layouts synchronized across multiple smart displays or vanity mirrors in real time. Often includes adaptive layouts, user profiles, and remote management.
• Traditional Mirroring: Basic screen-casting or screen-duplication (e.g., Chromecast, Miracast, AirPlay, HDMI) that sends one device’s display to another without advanced syncing of settings or multi-device state.

Key differences (side-by-side)

When to choose Magic Mirror Sync

• You need multiple mirrors/displays to show coordinated content (e.g., gym, hotel, retail, multi-room smart home).
• You want per-user profiles, persistent settings, and notifications across devices.
• You need remote management, scheduled content, or dynamic layouts.
• You prioritize a polished, tailored experience over minimal setup.

When to choose Traditional Mirroring

• You only need to duplicate a single device’s screen occasionally (presentations, casting a video to a TV).
• You want a simple, local-only setup or maximum privacy (wired HDMI or direct casting).
• Low-cost or one-off mirroring is the priority without cloud accounts.

Practical considerations

• Bandwidth: Magic Mirror Sync may need stable internet for cloud features; traditional mirroring can work locally or wired.
• Latency: For interactive use, test responsiveness—wireless casting can introduce delay.
• Compatibility: Check device and protocol support (SDKs, OS support, hardware).
• Security: Prefer encrypted casting or wired connections for sensitive content; evaluate cloud provider policies for synced systems.
• Cost: Magic Mirror Sync solutions often involve subscription or platform costs; traditional mirroring usually cheaper.

Recommendation

• Choose Magic Mirror Sync if you want a managed, multi-device, personalized experience with remote control and coordinated content.
• Choose Traditional Mirroring if you need simple, local screen duplication, lower cost, and minimal setup.

Date: March 14, 2026

How to Set Up Gmail Desktop Notifier on Windows and macOS

Overview

Gmail Desktop Notifier is not an official standalone Google app anymore, but you can get desktop notifications for Gmail on Windows and macOS using either Gmail’s web notifications in a browser, an email client configured for Gmail, or third‑party notifier apps. Below are step‑by‑step methods for both platforms.

Option 1 — Browser (Chrome, Edge, Firefox)

1. Sign in to Gmail in the browser.
2. Click the gear icon → See all settings → General → Desktop notifications.
3. Choose New mail notifications on (or Important mail only).
4. Click Allow when the browser prompts to let Gmail show notifications.
5. Verify OS notification settings:
   • Windows: Settings → System → Notifications → enable notifications for your browser.
   • macOS: System Settings → Notifications → enable for your browser.

Option 2 — Native Mail App (Windows Mail / Apple Mail)

1. Add your Gmail account:
   • Windows Mail: Settings → Manage Accounts → Add account → Google.
   • Apple Mail (macOS): Mail → Settings → Accounts → + → Google.
2. Follow Google OAuth sign‑in and allow required permissions.
3. Ensure Mail notifications are enabled in OS settings:
   • Windows: Settings → System → Notifications → Mail.
   • macOS: System Settings → Notifications → Mail.
4. Adjust folder sync (IMAP) in Gmail web settings if you want specific labels to appear.

Option 3 — Third‑party Notifier Apps (e.g., Mailbird, Mimestream, Kiwi)

1. Choose a trusted app for your OS and install it.
2. Add your Gmail account using OAuth (recommended).
3. Enable notifications inside the app and in OS notification settings.
4. Review app permissions and privacy settings before use.

Tips & Troubleshooting

• If notifications don’t appear, check browser/app is allowed to show notifications and not muted or Focus/Do Not Disturb mode.
• For multiple accounts, ensure the correct account has notifications enabled.
• If using an app with password-based IMAP, use an app password (if 2FA is enabled) from your Google Account.
• Keep browser/app updated; clear cache or reinstall if problems persist.

Quick Recommendation

For simplicity and privacy, use Gmail’s built‑in browser notifications (Chrome/Edge/Firefox) or a native mail app with OAuth.

Speedy Video Converter: Convert Files in Seconds

Overview

Speedy Video Converter is a lightweight tool designed to transcode videos quickly with minimal setup. It focuses on fast performance, straightforward presets, and a small footprint—ideal for users who need reliable conversions without dealing with complex settings.

Key Features

• Fast encoding: Optimized codecs and multithreading to reduce conversion time.
• Preset profiles: Ready-made profiles for common devices and platforms (MP4, WebM, mobile, social).
• Batch processing: Convert multiple files in one go.
• Quality control: Adjustable bitrate, resolution, and frame rate.
• Format support: Popular input/output formats (MP4, MKV, AVI, MOV, WebM).
• Lightweight UI: Minimalist interface with drag-and-drop support.

Performance Tips

1. Choose hardware-accelerated encoding (NVENC, Quick Sync, or VCE) if available to cut processing time significantly.
2. Use presets tailored to your target device to avoid manual tuning.
3. Lower resolution or bitrate for faster results when high fidelity isn’t required.
4. Batch smaller groups rather than dozens at once to reduce IO bottlenecks.
5. Close other CPU/GPU-heavy apps during large conversions.

Typical Workflow

1. Drag files into the app.
2. Pick an output preset (e.g., “MP4 — 1080p — YouTube”).
3. Optionally tweak bitrate or enable hardware acceleration.
4. Click Convert and monitor progress.
5. Find converted files in the output folder.

When to Use Speedy Video Converter

• Quick social media uploads needing fast transcodes.
• Converting large video batches overnight with minimal oversight.
• Users who prefer simple, fast tools over feature-heavy editors.

Limitations

• Not intended as a full video editor (no timeline editing).
• Advanced users may miss fine-grained codec controls.
• Output quality depends on source and chosen preset.

Conclusion

Speedy Video Converter shines when speed and simplicity matter: select a preset, enable hardware acceleration if possible, and convert files in seconds. For basic to intermediate conversion tasks it offers an efficient, user-friendly solution.

How to Use MP3Recorderer: Tips, Settings, and Best Practices

Quick setup

1. Install and open MP3Recorderer.
2. Allow microphone access when prompted.
3. Choose the input device (built-in mic, USB mic, or an audio interface).

Recommended settings

• Format: MP3 (default).
• Bitrate: 192–320 kbps for voice + music; 128–192 kbps for spoken-word only.
• Sample rate: 44.1 kHz standard; 48 kHz if matching video.
• Channels: Mono for single-voice; Stereo for music or multi-source recording.
• Gain/input level: Aim for peaks around -6 dB to -3 dB; avoid clipping (0 dB).

Recording tips

• Use a pop filter and position the mic 6–12 inches from the mouth.
• Record in a quiet, minimally reflective room; add soft furnishings to reduce echo.
• Monitor with headphones to catch issues live.
• Record a short test clip and check levels before long takes.

Workflow best practices

1. Create a naming convention: YYYYMMDD_project_take.mp3.
2. Use short takes and save frequently; enable automatic backups if available.
3. Record a few seconds of room tone for easier editing/noise reduction.
4. Keep a separate track for music or system audio when possible.

Editing and export

• Trim silences and remove clicks/pops.
• Apply light compression to even out levels (threshold and ratio conservative).
• Use noise reduction sparingly; preserve natural tone.
• Normalize or apply gentle limiting so final peaks sit near -0.1 dB.
• Export at the chosen bitrate; include ID3 metadata (title, artist, album) before distribution.

Troubleshooting common issues

• Distortion/clipping: lower input gain or move mic farther away.
• Background noise: try noise gate, spectral denoise, or re-record in quieter space.
• Low volume: increase gain or apply makeup gain in editing; avoid excessive boosting.
• Sync problems with video: record with a clapper or use a reference tone.

Security and file management

• Back up originals (lossless if possible) before destructive edits.
• Keep a master copy at high quality (e.g., WAV) and create MP3s from that master for distribution.

If you want, I can produce a step-by-step checklist tailored to podcasting, voiceover, or music recording.

PrettyMay Call Recorder for Skype for Business — Complete Guide & Setup Tips

What it is

PrettyMay Call Recorder for Skype for Business is a third-party application that captures and saves audio (and sometimes video) from Skype for Business calls and meetings. It’s typically used for compliance, training, record-keeping, or quality assurance.

Key features

• Automatic call recording: Start/stop recordings automatically based on call events.
• Multi-party capture: Records both local and remote audio streams; may support multi-user conference recording.
• File formats: Exports recordings to common formats (WAV, MP3) for archival and playback.
• Storage options: Local disk saving; some versions support network shares or integration with archiving systems.
• Indexing & metadata: Attaches call metadata (caller ID, timestamps, meeting subject) to recordings.
• Search & retrieval: Basic search tools to find recordings by date, participant, or keyword (feature set varies by version).
• Security & access controls: User/role permissions and file encryption in some deployments.
• Compliance features: Audit logs and retention controls for regulatory needs (availability depends on edition).

Typical use cases

• Regulatory compliance and audit trails
• Customer service quality monitoring and training
• Internal meeting record-keeping and minute preparation
• Dispute resolution and evidence preservation

System requirements (general guidance)

• Windows OS (server or desktop) compatible with the supported Skype for Business client/server version
• Sufficient CPU and disk space for continuous audio capture and storage
• Network access to Skype for Business servers if server-side integration is used
• Administrative rights for installation and integration with Skype for Business APIs

Installation & setup (step-by-step, assume Windows environment)

1. Download installer from vendor-provided source (verify checksum/signature).
2. Run installer as Administrator.
3. Choose installation type: standalone client (user-level) or server/centralized recorder.
4. Configure storage path: local folder or network share with appropriate quotas and backup.
5. Integrate with Skype for Business:
   • For client-side recording: ensure the recorder runs on each user’s machine and has permissions to access audio devices and Skype for Business process.
   • For server-side recording/archiving: provide service account credentials and configure SIP/UCMA or other supported APIs per vendor guide.
6. Set recording policy: automatic for all calls, only for specific users, or manual on-demand.
7. Configure metadata capture: map fields such as caller ID, SIP URI, meeting subject.
8. Set retention & access controls: apply encryption, user roles, and retention schedules.
9. Test recording: place test calls (one-to-one and group) and verify audio quality, file format, and metadata.
10. Deploy to users and provide training on playback and retrieval.

Configuration tips

• Use a dedicated service account for server-side integrations.
• Store recordings on high-availability storage with backups.
• Limit retention to what regulations require; purge older files automatically.
• Monitor disk and CPU usage; schedule maintenance windows for large archives.
• Ensure time synchronization (NTP) across systems for accurate timestamps.

Troubleshooting common issues

• No audio recorded: check recorder permissions, audio device settings, and whether Skype for Business is using exclusive audio mode.
• Poor audio quality: inspect network latency/packet loss, verify codecs, and check endpoint microphone settings.
• Missing metadata: confirm API permissions and that the recorder is correctly hooked into Skype server events.
• Failed uploads to network share: verify network credentials, share permissions, and firewall rules.
• High storage usage: enable compression (MP3), lower quality settings, or implement retention policies.

Security & compliance considerations

• Encrypt recordings at rest and in transit.
• Restrict access with role-based controls and audit logging.
• Maintain clear policies informing participants when calls are recorded to meet legal requirements.
• Ensure retention and deletion practices comply with applicable laws (e.g., GDPR).

Alternatives

• Native Skype for Business Server/Cloud recording features (if available)
• Other third-party recorders specialized for UC platforms (e.g., Verint, NICE, OrecX)
• Cloud meeting platforms with built-in recording (Teams, Zoom) if migration is an option

Final checklist before production

• Installation completed and service started
• Test recordings verified for different call types
• Storage, backup, and retention confirmed
• Security, encryption, and

Linksys WET610N vs Modern Alternatives: Is It Still Worth Using?

Quick verdict

The Linksys WET610N can still be useful for very specific, budget-conscious scenarios (simple wireless bridging for older gear), but for most users modern alternatives offer better speed, security, reliability, and easier setup.

What the WET610N is

• Device type: Wireless-N bridge / access point (2.4 GHz, single-band)
• Main use: Connect wired devices (printers, older game consoles, set‑top boxes) to a Wi‑Fi network or act as a basic range extender.
• Connection: Ethernet port for LAN device; supports WEP/WPA/WPA2 (older implementations).

Strengths of the WET610N

• Low cost: Often inexpensive on the used market.
• Simple bridging: Straightforward at linking a single Ethernet-only device to Wi‑Fi.
• Compact and power-efficient: Small footprint and low power draw.

Key limitations compared to modern alternatives

• Single-band 2.4 GHz only: Prone to congestion and interference; no 5 GHz support.
• Older Wi‑Fi standard: 802.11n (max theoretical ~150–300 Mbps) — real speeds usually much lower.
• Security: Lacks modern security features like WPA3 and more robust, updated firmware.
• Limited features: No mesh support, MU-MIMO, beamforming, or advanced QoS.
• Age and reliability: Used units may be near end of life, with potential hardware failure and no firmware updates.

What modern alternatives offer

• Dual- or tri-band radios (2.4 + 5 GHz ± 6 GHz): Better performance and less interference.
• Faster standards (Wi‑Fi 5/6/6E): Higher throughput, lower latency, and better multi-device handling.
• Improved security: WPA3, more frequent firmware updates, and better encryption.
• Mesh and extender ecosystems: Seamless roaming and easier coverage expansion.
• Advanced bridging modes and power-over-Ethernet (PoE): Flexible deployment options for smart homes and small offices.

Use cases where the WET610N is still acceptable

• You need a very cheap bridge for a single legacy Ethernet device that only needs basic connectivity.
• The environment has minimal 2.4 GHz congestion and your bandwidth needs are low.
• You prefer a one‑time cheap purchase and accept security limitations (not recommended for sensitive data).

Use cases where you should choose a modern alternative

• You use streaming 4K, cloud gaming, video conferencing, or multiple simultaneous devices.
• You need robust security (WPA3), regular firmware updates, or enterprise-grade features.
• You plan to build or expand a mesh network for whole-home coverage.
• You want lower latency and better performance for modern Wi‑Fi ⁄₆ devices.

Recommended modern alternatives (by need)

• Cheap single-device bridge / extender: Newer Wi‑Fi 5 extenders or a low-cost travel router with client mode.
• Home mesh and whole-home coverage: Wi‑Fi 6 mesh systems (e.g., consumer Wi‑Fi 6 mesh brands).
• High performance / gaming: Wi‑Fi 6 routers with dedicated backhaul and QoS.

Comparing XRI Explorer Alternatives: Which One Fits You?

Choosing the right XRI Explorer alternative depends on your goals, technical skill, budget, and preferred workflow. Below is a concise comparison of five notable alternatives, what they excel at, and which user each one best fits.

1. XRInsight

• Strengths: Robust analytics, real-time telemetry, customizable dashboards.
• Weaknesses: Steeper learning curve, higher pricing for enterprise tiers.
• Best for: Data-driven teams and enterprises that need deep insights and scalable reporting.

2. NavigatorX

• Strengths: Intuitive UI, strong mapping/visualization tools, good mobile support.
• Weaknesses: Limited advanced analytics, fewer integration options.
• Best for: Field teams and nontechnical users who prioritize ease of use and visual exploration.

3. ProbeSuite

• Strengths: Lightweight, fast performance, open-source SDKs, extensible via plugins.
• Weaknesses: Requires developer resources for customization; limited official support.
• Best for: Developers and organizations that want a highly customizable, cost-effective solution.

4. AtlasR

• Strengths: End-to-end platform with built-in data pipelines, strong security/compliance features.
• Weaknesses: Can be overkill for small projects; longer deployment time.
• Best for: Regulated industries and large teams that need integrated data processing and strict governance.

5. ExplorerLite

• Strengths: Affordable, easy setup, good for quick prototyping and small datasets.
• Weaknesses: Lacks enterprise features and advanced scalability.
• Best for: Individuals, startups, or small teams experimenting with XRI workflows on a budget.

How to Choose — Quick Checklist

1. Purpose: Do you need analytics, mapping, development flexibility, compliance, or low cost?
2. Skill level: Prefer no-code visual tools or developer platforms?
3. Scale: Single projects, growing teams, or enterprise-scale deployments?
4. Budget: Free/open-source, subscription, or enterprise licensing?
5. Integrations: Does it need to connect with existing stacks (APIs, data warehouses, mobile apps)?

Recommendation Scenarios

• If you want enterprise analytics: XRInsight
• If you need visual mapping & field use: NavigatorX
• If you prefer open-source and customization: ProbeSuite
• If you require security and integrated pipelines: AtlasR
• If you’re on a budget or prototyping: ExplorerLite

Choose the option that aligns most closely with your primary constraint (skill, scale, budget, or compliance). If you tell me which constraint matters most, I can recommend a single best fit and outline next steps.

Fat32Formatter vs. Other Tools: Which Is Best for FAT32 Formatting?

Formatting drives to FAT32 can be tricky when dealing with large USB sticks, external HDDs, or SD cards. Several tools claim to make the job easy; here’s a practical comparison to help you choose the right one for your needs.

Why FAT32?

• Compatibility: Widely supported by Windows, macOS, Linux, game consoles, cameras, and many embedded devices.
• Limitations: Single-file size limited to 4 GB and partition size effectively limited by many OS tools (Windows’ built-in formatter restricts FAT32 creation to 32 GB).

Tools Compared

• Fat32Formatter (GUI utilities often called “Fat32Formatter”)
• Windows built-in Format tool
• diskpart (Windows command-line)
• mkfs.fat / mkfs.vfat (Linux)
• Rufus
• GUI-format / GUI FAT32 Format (third-party Windows GUI)
• GParted (Linux GUI)
• Third-party partition managers (AOMEI, MiniTool, EaseUS)

Ease of Use

• Fat32Formatter / GUI FAT32 Format: Very user-friendly; one-click formatting and useful for novices. Minimal configuration options but gets large drives formatted to FAT32 without fuss.
• Windows Format: Easiest for common tasks under 32 GB. GUI is familiar but blocks FAT32 for larger volumes.
• diskpart: Powerful but requires command-line steps; riskier for inexperienced users.
• mkfs.fat / mkfs.vfat: Standard on Linux; straightforward for users comfortable with terminal.
• Rufus: Designed for creating bootable USBs; formatting options are clear and modern UI.
• GParted: Full-featured GUI partitioning suite; more steps but precise control.
• Third-party partition managers: Feature-rich with wizards; may include extra utilities (cloning, resizing).

Supported Sizes and Limits

• Fat32Formatter / GUI FAT32 Format: Can create FAT32 on very large volumes (hundreds or even thousands of GB), bypassing Windows’ 32 GB GUI limit.
• Windows Format: Limits FAT32 creation to 32 GB in the GUI; can only format larger drives as exFAT or NTFS.
• diskpart: Can format large drives, but behavior varies; careful syntax required.
• mkfs.fat: No small-size restriction; handles large volumes when given proper options.
• Rufus/GParted/Third-party tools: Typically support large volumes; check individual versions for limits.

Speed and Performance

• Formatting speed is mostly influenced by drive size and filesystem parameters (cluster size). Most tools produce similar results when using similar cluster sizes.
• Fat32Formatter / GUI tools: Often set sensible defaults for cluster size to balance space utilization and performance.
• Advanced tools (mkfs, GParted): Allow explicit cluster size tuning for optimal throughput on specific devices.

Reliability and Safety

• GParted, mkfs.fat, diskpart: Mature, widely used, reliable. Offer more feedback and error messaging.
• Fat32Formatter / GUI-format: Reliable for simple tasks but may offer less granular feedback on low-level errors.
• Third-party utilities: Vary by vendor—read reviews; prefer well-known names.

Features & Advanced Options

• Partitioning control: GParted and third-party partition managers excel.
• Cluster size selection: Available in most tools; mkfs and advanced GUIs give the most control.
• Quick vs full format: Most tools let you choose. Full format checks for bad sectors and takes longer.
• Bootable media creation: Rufus is best-in-class for creating bootable FAT32 USBs.

Compatibility Concerns

• Some embedded devices and cameras expect specific cluster sizes or reserved sectors. If a device fails to read the drive, try formatting with a different cluster size or use the device’s own formatting tool.

When to Use Which Tool — Quick Recommendations

1. You want a quick FAT32 on a >32 GB drive (Windows user): Use Fat32Formatter or GUI FAT32 Format.
2. You prefer built-in tools and drive is ≤32 GB: Use Windows’ Format.
3. You’re on Linux or comfortable with terminal: Use mkfs.fat for full control.
4. You need partitioning or complex setups: Use GParted or a reputable partition manager.
5. You need a bootable USB: Use Rufus.
6. You need enterprise features (cloning, recovery): Use third-party partition suites like AOMEI or MiniTool.

Troubleshooting Tips

• If device won’t mount after formatting: try different cluster sizes, run a full format, or check for hardware write-protection.
• For persistent errors, test the drive for bad sectors (chkdsk /r on Windows or badblocks on Linux).
• If a device only accepts small partitions, try formatting a smaller partition size or check device documentation.

Security and Data Safety

• Formatting erases file-system structures; it doesn’t securely erase data. Use secure-wipe tools if you need to prevent recovery.
• Always back up important data before formatting.

Verdict

• For most Windows users needing FAT32

How to Integrate Gantt Chart Light Library in Your JavaScript Stack

Overview

A concise guide to add a lightweight Gantt chart component to a modern JavaScript app (vanilla, React, Vue, or Svelte). Assumes the library is distributed as an ES module and offers a small CSS file plus an API to create charts, add tasks, and respond to events.

1. Install

• npm: npm install gantt-chart-light
• yarn: yarn add gantt-chart-light
• or include via CDN: “ and link CSS.

2. Basic usage (vanilla JS)

html
Copy CodeCopied
<link rel=”stylesheet“ href=”nodemodules/gantt-chart-light/dist/gantt-chart-light.css“>
<div id=”gantt“></div>
<script type=”module“>
import { Gantt } from ‘gantt-chart-light’;
  const gantt = new Gantt(document.getElementById(‘gantt’), {
    start: ‘2026-03-01’,
    end: ‘2026-04-01’,
    view: ‘weeks’
  });
  gantt.loadTasks([
    { id: 1, name: ‘Design’, start: ‘2026-03-02’, end: ‘2026-03-10’, progress: 50 },
    { id: 2, name: ‘Develop’, start: ‘2026-03-11’, end: ‘2026-03-25’, depends: [1] }
  ]);
</script>

jsx
 ffON2NH02oMAcqyoh2UU MQCbz04ET5EljRmK3YpQ CPXAhl7VTkj2dHDyAYAf” data-copycode=“true” role=“button” aria-label=“Copy Code”>Copy CodeCopied
import React, { useRef, useEffect } from ‘react’;
import { Gantt } from ‘gantt-chart-light’;
import ‘gantt-chart-light/dist/gantt-chart-light.css’;

export default function GanttChart({ tasks, options }) {
  const ref = useRef(null);
  useEffect(() => {
    const gantt = new Gantt(ref.current, options);
    gantt.loadTasks(tasks);
    return () => gantt.destroy();
  }, [tasks, options]);
  return <div ref={ref} />;
}

js
Copy CodeCopied
import { Gantt } from ‘gantt-chart-light’;
export default {
  props: [‘tasks’,‘options’],
  mounted() {
    this.gantt = new Gantt(this.\(el</span><span class="token" style="color: rgb(57, 58, 52);">,</span><span> </span><span class="token" style="color: rgb(0, 0, 255);">this</span><span class="token" style="color: rgb(57, 58, 52);">.</span><span>options</span><span class="token" style="color: rgb(57, 58, 52);">)</span><span class="token" style="color: rgb(57, 58, 52);">;</span><span> </span><span>    </span><span class="token" style="color: rgb(0, 0, 255);">this</span><span class="token" style="color: rgb(57, 58, 52);">.</span><span>gantt</span><span class="token" style="color: rgb(57, 58, 52);">.</span><span class="token" style="color: rgb(57, 58, 52);">loadTasks</span><span class="token" style="color: rgb(57, 58, 52);">(</span><span class="token" style="color: rgb(0, 0, 255);">this</span><span class="token" style="color: rgb(57, 58, 52);">.</span><span>tasks</span><span class="token" style="color: rgb(57, 58, 52);">)</span><span class="token" style="color: rgb(57, 58, 52);">;</span><span> </span><span>    </span><span class="token" style="color: rgb(0, 0, 255);">this</span><span class="token" style="color: rgb(57, 58, 52);">.</span><span>gantt</span><span class="token" style="color: rgb(57, 58, 52);">.</span><span class="token" style="color: rgb(57, 58, 52);">on</span><span class="token" style="color: rgb(57, 58, 52);">(</span><span class="token" style="color: rgb(163, 21, 21);">'taskChange'</span><span class="token" style="color: rgb(57, 58, 52);">,</span><span> </span><span class="token parameter">task</span><span> </span><span class="token" style="color: rgb(57, 58, 52);">=></span><span> </span><span class="token" style="color: rgb(0, 0, 255);">this</span><span class="token" style="color: rgb(57, 58, 52);">.</span><span class="token" style="color: rgb(57, 58, 52);">\)emit(‘update:task’, task));
  },
  beforeUnmount() { this.gantt.destroy(); }
}