Beams crash

lanternz · Post by **lanternz** » Tue Apr 07, 2009 12:55 am

I have had a few but I think this one is repeatable. Inadvertently select the text for a channel number for example. Then try to use the find function.

Post by **admin** » Tue Apr 07, 2009 9:36 pm

Thanks for taking the time to point this out. When something is repeatable, it is much easier to track down and fix. LXFree 1.1.7 fixes this bug.

lanternz · Post by **lanternz** » Thu May 07, 2009 4:49 am

another crash brought about by clumsy fingers. select an instrument then try to get an equipment count in the reports. bye-bye beams.

lanternz · Post by **lanternz** » Thu May 07, 2009 4:55 am

Another I found the other day. Grouping an instrument with it's gobo symbol - as occurs when using using the insert gobo symbol menu item, stops beams from working.

lanternz · Post by **lanternz** » Thu May 07, 2009 4:57 am

crash on equipment count report may also be to do with an .lxx file from MacLux Pro with some old custom MLP symbols.

Post by **admin** » Fri May 08, 2009 5:39 pm

The crash with an imported LXX file and the symbol report is due to a division by zero error. This is now trapped so it won't crash. Having a symbol selected or not would not affect this crash, it would happen with a plot imported from MacLux Pro.

Striplights have a more advanced treatment in the LXSeries. The specific thing that caused the crash was the Sections per Fixture field was at zero because MacLux Pro does not support a this information.

To make striplights imported from MacLux Pro behave properly in LXSeries applications, you'll need to edit the key. You can do this by saving the key and opening it with LXKeyEditor. Or, you can add columns to a Symbols report and edit that way. In addition to Sections per Fixture there is Lamps per Circuit and Distance Between Lamps. (The latter are important for LXBeams to be able to show the beams of the striplight.)

Post by **admin** » Fri May 08, 2009 6:43 pm

I have not been able to duplicate your grouping crash. Is there anything more specific you can add that might help reproduce it? Or, do you have the crash log. That may or may not help.

lanternz · Post by **lanternz** » Sun May 10, 2009 3:07 am

It's not really a crash so much as an, at first puzzling, unresponsiveness. Add a gobo to an instrument, select the insert gobo symbol function from the format menu and the instrument will now not respond to a view beam command until it has been un-grouped.

Post by **admin** » Sun May 10, 2009 12:52 pm

Hold down the option key and click on an object inside a group to edit it individually.

Say, for example, you have a color scroller grouped with an instrument. If you select the group and edit the channel, it will change the channel for both. If you option-click the scroller, you can edit just its channel.

Most commands are passed on to the entire group this way. Create Beams is not. In the case of a single light grouped with an accessory, this might not seem to make sense. But if you have an entire grouped position, a six par bar being a common example, then Create Beams would add beams for the entire group (unless a single object was selected by option-click).

Post by **admin** » Mon May 11, 2009 12:56 pm

Update: The newest LXBeams 0.9.2910 will create a beam for a light inside a selected group if the group contains only one symbol that can create a beam.

This resolves the conflict of expectations that appears in the last post by having LXBeams look at the context and deciding how to respond.

Directly selecting an object inside a group by option-clicking remains an important shortcut to being able to edit an object without ungrouping to isolate it.

In the case of a group inside a group, it is necessary to ungroup to access objects inside the nested group (but not the outer group).

lanternz · Post by **lanternz** » Wed Aug 19, 2009 2:10 am

Another consistent crash. Two versions of the same drawing for two different venues. I have a ground row arrangement of 24 single flood units. I delete the old arrangement for the next venue and then try to copy and paste the new arrangement from the current venue into the next venue. Firstly the drawing of the next venue is very slow in deleting the old arrangement. But then the app crashes when I paste the new arrangement.

Post by **admin** » Thu Aug 20, 2009 3:25 pm

Hi,

I can't repeat this one. Where and how is the channel text selected? Is the find panel already visible?

Thanks.

lanternz · Post by **lanternz** » Sat Aug 22, 2009 4:01 am

I have two drawings - on one I click and drag to select a position and 24 floodlights with channel and colour information. I copy that selection. Switch to the second drawing and paste the selection. Spinning beach ball for a very long time and then crash. I can successfully copy small chunks in this way, around 4 instruments at a time but it is still very slow to paste.

Post by **admin** » Sat Aug 22, 2009 10:54 pm

Hi,

I was looking at an old post. I see now that the latest is about delete, copy and paste. I should probably figure out a way to archive posts or start a new thread when a new issue comes up. Otherwise, this thread is a list of problems found and solved and isn't relevant to the current software version anyway.

I have no idea particularly about this behavior. It may have to do with the specific plot and the cut and paste problem is really the result of something else. I can cut and paste many objects from one plot to another consistently with no problems.

You can send the crash info if you want. Sometimes that's a help and often not. You can send the plots and I can see if I can get the crash to happen which is a sure way of tracking it down because I can completely trace the execution (provided, of course, I can get the crash to happen for me.).

lanternz · Post by **lanternz** » Sun Aug 23, 2009 7:34 am

OK will do. Files on their way to you.