In basic ide F5 shortcut key as well the equivalent icon on the toolbox runs the first macros (Function or Procedure) in a module always, in spite that cursor might stand within other procedure. Reproduction 1. Open a basic macros module (Probably a new one) 2. Type code: Sub test1 msgbox "test1" end sub Sub test2 msgbox "test2" end sub 3. Put cursor within the second subprocedure (test2) 4. Press F5 key or a Run Basic icon on the Macro toolbox Result: test1 macros will work and output a message "test1". Although I tested it only on linux OS, I believe it's a cross-platform issue. Oto
(In reply to comment #0) > In basic ide F5 shortcut key as well the equivalent icon on the toolbox runs > the first macros (Function or Procedure) in a module always, in spite that > cursor might stand within other procedure. This is actually by design, personally I don't like this behavior, I'm all for changing it. But really, not a bug but an enhancement.... I'll take it anyway
fixed..
and if we can't figure out what macro you mean ( e.g. the cursor is above or below a procedure ) we open a chooser
there isn't such behavior in OOo 3.2.1 that is why i judged it as a bug. And it's very unhandy to pic macros from menus all the time in a development environment, you know.
Verified in the last 10_10_28_Cedric .rpm build - F5 and the icon run the second macro if the cursor is in it. If it's between, a dialog open to choose which macro to run - Closing - Sophie
(In reply to comment #5) > Verified in the last 10_10_28_Cedric .rpm build - F5 and the icon run the > second macro if the cursor is in it. If it's between, a dialog open to choose > which macro to run - Closing - Sophie actually it was previously marked as NOT A BUG afaik because such behavior was due to design, but then some devs changed it to what it is now.
(In reply to comment #6) > (In reply to comment #5) > > Verified in the last 10_10_28_Cedric .rpm build - F5 and the icon run the > > second macro if the cursor is in it. If it's between, a dialog open to choose > > which macro to run - Closing - Sophie > > actually it was previously marked as NOT A BUG afaik because such behavior was > due to design, but then some devs changed it to what it is now. Yes, this is why I checked that the fix runs as expected in the last build, it's implemented and works correctly so the issue is now closed - Sophie