Known Issues

The items listed on this page represent issues we have been able to reproduce and confirm, and impact a large number of users. A work-around or suggestion for avoiding the issue, if known, will also be included in the listing. Click on the item to toggle between expanding or collapsing the information related to the item.

Last updated: June 16, 2014

  • When I open my project the progress bar just keeps cycling through but my project never opens
    • Your project is stored as XML in the Lumzy database, and if there are characters introduced in the page or component labels that conflict with the XML, this can cause the project file to be corrupted and unable to be opened.

      Workaround: To prevent this situation, you should avoid using characters such as (", ', <, >, /) in your labels for your pages and components.

      Since you won't be able to open your project and revert to an earlier version, your only option will be to contact the Support team (normal support hours are M-F 9AM to 5PM PST).

  • Foreign characters not displaying correctly when I open a project
    • Lumzy currently does not officially support foreign language characters at this time.

      Workaround: Try using the Windows® emulation mode, you may find your characters showing up, though it may not be all characters for the language you're working with, so you'll want to do a lot of testing. To change the emulation mode of your prototype, look to the lower right of the Lumzy tool window and you'll see three icons (Pencil, Windows® logo, Apple® logo). Click on the Windows® logo to change the look of your project and you may find the character support you're looking for, but please test all the characters you need and in all the objects and labels before proceeding.

  • Can't save project OR receiving a "can't communicate with server" error...
    • This error message indicates when your client has lost its connection with the server.

      Workaround: To re-establish a connection for your current session, you can open up a new browser session (do NOT close the one you're working on), and log in to the tool. The majority of the time, the original session will recognize a new session has been established and will be able to piggyback off the newly created session, and you should now be able to save your work.

  • Export to PDF or JPG doesn't seem to work - nothing happens when I click...
    • This includes a couple different scenarios. 1) After exporting to PDF, when I click the "Download" page, nothing happens; 2) When I try to export to JPG it doesn't do anything.

      The simplest cause for issue #1 is usually a local operating system (OS) issue, where either the OS didn't sense that it s being asked to download a file, or the OS has opened a typical download window for you to specify where to save the file, but this window is hiding behind some other window on your screen. For these, you simply need to try again, and make sure you're the window isn't being hidden (most common on Linux systems).

      The other cause for issue #1 (when the Download button truly is not doing a thing), or issue #2 (when export to JPG doesn't do anything at all), is the use of the "/" character in either the project title or a page title.

      Workaround: First make sure your OS isn't displaying the download window behind some other existing window on your screen.
      Second, make sure you don't have any "/" characters in your project or in any page titles within your project.

  • Undo/Redo seems to be ignoring certain changes
    • When using the Undo or Redo feature, it seems to be missing some of the changes that were made, so it is not fully undoing or redoing all the changes expected. This function only records the last position of a component on a page, so undoing a bunch of moves of a component around a page are ignored. For example: if you place a component on a page; move it to the top left corner; then move it to the top right corner; then move it to the bottom left corner. Using Undo will simply remove the component from the page, and then using Redo will place the component back on the page in the bottom left corner (the last position where this component was located).

      When working with container components, changes within a container follow the same characteristics, however, if a parent container is deleted, the Undo function will undo the delete of the container component itself, but not of the children it contained, so it will be restored but empty of any children components it may have had.

      Workaround: none at this time - just need to be aware of the limitations and quirks.

  • Components disappear when selecting a group and trying to move them
    • When selecting a group of components to move around on the page, following or during the move, there's a scenario where the components seem to disappear during the move. This seems to generally be the case if the group is quickly moved, and may be indicative of the positional code getting overloaded.

      Workaround: To make the components reappear, use the mouse to drag select the area where the components were when they disappeared - you should see that something appears to be selected. Now use the Cut and then the Past functions from the Action Toolbar, and the components will now be visible again on the page.

  • Adding an icon/image - I don't see the popup to select the icon image
    • The simplest cause is usually a local operating system (OS) has opened the icon/image window, but this window is hiding behind some other window on your screen.

      Workaround: Make sure the popup window isn't displaying the download window behind some other existing window on your screen.
      If you're sure the window is not showing anywhere, then it is likely that you need to restart your browser to clear out the cache for the Adobe Flash plugin used by the Lumzy application. Log out of the Lumzy app, close your browser, and then start it up again and log in

  • Issues with placement of Annotations by a reviewer
    • When you have a reviewer looking at your prototype and adding Annotations, if they attempt to place an Annotation inside the following container components, the Annotation will be placed on the page in the upper left quadrant. The components include: the Browser; Form; Accordian; and Tab Navigator. An Annotation can be placed in the header of the Browser, or on a section heading on the Accordian, but can not be placed inside these containers, nor inside the Form or Tab Navigator. Attempting to do so will show the Annotation added to the page in the upper left quadrant.

      Workaround: There is no solution at this time. You can get around this issue for the Browser and Form components, by placing a rectangle in front of these containers, such that the rectangle appears to be the space inside the container, and then place all your components (that you'd normally place inside the container) inside the boundaries of the rectangle. You must make sure when you add the rectangle, it's added to the page and not inside the container, otherwise it will become a child of the container and will not solve this issue. This rectangle approach will not work for either the Tab Navigator or the Accordian.

  • Change Skin - can't see certain attributes like text or borders
    • When using the "Change Skin" option to change the theme of the Lumzy interface from the standard to the dark skin, the dark skin may conflict with some objects using darker colors for attributes such as text or borders. These attributes are all visible when using the design mode with the standard skin, but are not visible (or not as easily visible) under the dark skin. There is a specific issue when using the dark skin during simulation, where a TextField will be all black (which is the same as the text), so you won't be able to view the text.

      Workaround: if you notice you have trouble with the darker skin then use the standard skin, especially during simulation.

  • Difficulty changing color properties (ex. fill, or line, or font)
    • When changing the color property of a component, such as the fill, line, or font color), the newly selected color doesn't always change to the selected color.

      Workaround: Try selecting a different color (or two), and then select the color you want. This just seems have a little "stickiness" to it, but clicking around on a couple different colors will "unstick" things so you'll be able to set the color you want

  • Unable to use a "Draw" component on the page and then cursor is stuck in "+" mode
    • There is currently an issue where the Draw components (ex. "Draw Triangle", "Draw Circle", "Draw Rectangle") can't be dragged from the library onto any page that is referencing a master page. In this scenario, attempting to drag one of these Draw components onto a page that is referencing a master page, results in nothing being added to the page, plus the cursor remains looking like it's in the "draw" mode with the "+".

      Workaround: For any page where you need to add a Draw component, first turn off any reference to a master page. Then drag the Draw component to the page. After that, you can turn the reference to the master back on, and should be able to work with the Draw component within the page (i.e. resize, move, change colors, etc...) - the issue is just the initial placement onto the page.

  • Duplicating a page only copies components and not the container
    • Please see the "General container issues" in the COMPONENTS section below, as this is an issue related to using a container component.
  • My pages are missing or work is missing
    • The Sharing feature should only be used as a way to share a project - simultaneously working on a project can result in overwriting each other's changes.   Even if you are not sharing, and you still have a similar issue, please make sure you haven't left your project open on another computer (like your computer at work vs. your computer at home), or that you don't have it open in another browser session on your same machine. Having multiple copies of a single project open in multiple different places will overwrite each other and the last copy that saves will be what is on the server..

      Workaround: Never open a project in multiple places, and if you mistakenly have done so and appear to have lost work, try using the newly released History function from the main menu to grab an earlier copy of your session.

      Also make sure you're aware of, and using the Version feature for making copies of your project after you've made a lot of important changes. There's also the Clone feature for creating completely separate copies of a project.

  • General container issues
    • Components are in different layer order in simulation than when in design
      • This show up in the form of either a component not showing up on a page when in simulation, or if you've got a Hot Spot component that doesn't seem to be taking a click action, it may be in the background during simulation. This problem seems to associated with having at least two container components, with one as the child of the other.

        Workaround: Reverse the layering of the problem component (i.e. if it's hiding behind something when in simulation, then place behind the component in the design so when the simulation is run, it will now appear on top.

        Another option is to rebuild the page, making sure not to use any of the layering buttons (i.e. the "Move back one layer", "Move to the front", etc...). This issue seems to be caused by a unique combination of using containers and changing the layer of a component.

        In general, we recommend limiting the use of container components as active parents, and to instead use them as static background images. You can do this by basically taking care to add components first to the page, then once on the page, you can move the component so it sits on top of the container - this way the container acts as a static background. This will also significantly reduce the size and increase the performance of your prototype.

  • Tab Navigator issues
    • Highlighting text of a child component moves the Tab Navigator
      • When in edit mode on a label for a child component within a Tab Navigator, dragging with the mouse to highlight the text you want to edit, will end up dragging the entire Tab Navigator around.

        Workaround: You must either use the cursor keys to highlight just the text you want to edit, or if you're changing the entire label then just use the standard double-click to select all the text.

    • Can't get out of edit mode for child component
      • Difficult to get out of edit mode for child components of a Tab Navigator, especially for those components such as a List or ComboBox, where hitting the Enter or Return key simply adds another line.

        Workaround: When you're done editing the component, click somewhere on the page outside the Tab Navigator component to end the edit mode for the component. Avoid clicking or double-clicking on some other component, and instead pick an empty space on the page, as double-clicking on some other component will not only end your edit mode, but you'll lose your changes.

  • Radio Buttons all work as a single group
    • Radio buttons do not currently support more than a single group within a project. In other words, if you place two separate groupings of radio buttons on a page, or even on multiple pages, they will all work as a single group, and clicking on any radio button will uncheck whatever other radio button is currently checked.

      Workaround: There is no workaround. From a simulation standpoint, this is less confusing as long as the radio button groups are placed on different pages. When on different pages, the user only sees a group of radio buttons, and when they click on one it displays as checked, and when they click on another it appears as though they're all part of the same group. If they move back to a previous page where they had checked a radio button, they'll notice that button is no longer set, but again this seems to be much less of an issue when a user is simply trying out a prototype.

  • Duplicating a page only copies components and not the container
    • When using the "Duplicate Current Page" function within a project, there is a scenario where the entire page is not being copied to the new page. This applies to pages that have a container component (ex. Browser, Plain Canvas, etc...), AND the container component has child components within it. If any of the child components is currently selected, and then the user clicks the "Duplicate Current Page" button, all the components except the container will be duplicated onto the new page.

      Workaround: Prior to duplicating a page, make sure none of the child components are actively selected (i.e. if they are showing the move/sizing handles, then they're actively selected). Another option, which we always recommend when possible, is to avoid using child components, and instead use containers as background components that the other components simply sit on top of.

  • Images not showing up when buried deep in a hierarchy on shared projects
    • There is currently a known limitation to the hierarchical depth to which an uploaded image will be viewable in simulation by someone using a URL to view the project.

      When uploaded images are used in a project, and the project is shared via a URL, if the image is four layers deep, or lower, in a hierarchy of containers within containers, then the image will not be viewable via the URL. Let's see if we can make this a bit clearer, using the image below...

      Level 1 is the page; Level 2 is the Tab Navigator container; Level 3 is the Form container; any images in the Form (i.e. at Level 3) or above should be visible, but going lower (as shown by the image at Level 4 in the Accordion container) will have issues being viewed when shared via a URL.

      Workaround: If the image exists at a higher level anywhere else in the project, then the same image used at a very low level will still be rendered and viewable, so you could create a page of all your lower level images, keeping them all just on the page (i.e. not inside other containers). This page doesn't even have to be referenced by any of the other pages in your project - it just has to exist in your project. When your project is shared they will be viewable on the pages where they exist in the lower levels.

  • Can't click my HotSpot during simulation or Components seem out of order
    • Components sometimes show up in a different layered order during simulation than in the design mode. This appears to be an issue when using multiple container components together (i.e. a parent container with a child container).

      Workaround: When possible, avoid using containers, especially nested groups of containers. For many of the containers, you can use them statically in the background, by avoiding to drag any child components into them (i.e. drag a component somewhere on the page outside of the container first, then drag the newly added component in front of the container). Another option is to use the Draw components to draw your own versions of the containers, since many of these merely provide visual bordering to break up screens of components.

      The other option is to reorder the components in the design so that they work in the order the simulation seems to be using.

  • Simulation screen appears significantly smaller at times
    • There have been reports of the simulation window sometimes appearing very small during a simulationg session. This has been challenging to replicate, but it seems to coincide with running simulation after working on a page that uses significantly smaller dimensions than the default window size, such as when you've created a popup window for your project.

      Workaround: Restart your Lumzy session to flush out the cache, and you should be good to go.

About Lumzy | Terms of Use | Privacy Policy | Support | FAQs
Copyright © 2010-2016. All Rights Reserved, Crunch Frog, LLC