Since recent Corona builds, the Simulator device window does not remember its last position?

Solar2D General Questions/Discussion
#1

Since recent Corona builds (I guess the new skin?)…

(1) Run Corona simulator (via ZeroBrane editor run button)

(2) A device window comes up

(3) Position it to the position I want (the right part of my screen)

(4) Stop Corona simulator (via ZeroBrane editor stop button)

(5) Run Corona simulator (via ZeroBrane editor run button)

(6) The device window still goes back to the left part of my screen   <---- WHY???

It’s not like this before. This is happening with recent builds after some new skins are introduced.

I have to re-position the device window every time. Please help… 

PS. I am using build 2511 in Mac.

#2

Have you posted this as a bug report?

http://developer.coronalabs.com/content/bug-submission

#3

So it’s a bug every Mac user is facing? 

All Mac users have the same problem and no one complains?   It’s weird…

#4

If I don’t use ZeroBrane to start Corona, the last position is remembered.

Corona should consider all use cases when making changes.

Please correct this as soon as possible. It’s very annoying that the device window has to be dragged every time the code is run during intense code modification in development phase.

#5

No, I did not imply that. I asked if you have filed a bug report as you believe you have found a bug. I do not consider the behaviour a bug and it does not bother me as my Corona simulator starts up in the same location every time. I’m not using ZeroBrane.

Have you checked the parameters that your IDE passes to Corona?

Given that you are the only person complaining that ZeroBrane does not work nicely with Corona perhaps it is your setup and not everyone else’s.

Being a software tester, why should Corona consider a use case outside their control?

#6

I didn’t change the setup and it broke after some new skins are introduced in the Corona build

And I have two Mac computers, both was working fine and suddenly Corona couldn’t remember last position.

I don’t think it’s a setup problem.

If there is extra setup I have to add, I hope Corona can teach me (or where should I find it out?)

#7

@joe528, try closing the simulator after you move it without using “Stop” in ZBS. ZBS will detect that the application is closed and will stop the debugging, but it may give the Simulator a chance to save its new position. I’m not sure what changed in the recent Corona SDK build, but see if this helps. Paul.

#8

@paulclinger

That will work. Thanks.

But hope either Corona or ZBS can correct this somehow, or I have to remember to close it without using stop when I want the last position to be remembered.

#9

Have you posted this as a bug report?

http://developer.coronalabs.com/content/bug-submission

#10

So it’s a bug every Mac user is facing? 

All Mac users have the same problem and no one complains?   It’s weird…

#11

If I don’t use ZeroBrane to start Corona, the last position is remembered.

Corona should consider all use cases when making changes.

Please correct this as soon as possible. It’s very annoying that the device window has to be dragged every time the code is run during intense code modification in development phase.

#12

No, I did not imply that. I asked if you have filed a bug report as you believe you have found a bug. I do not consider the behaviour a bug and it does not bother me as my Corona simulator starts up in the same location every time. I’m not using ZeroBrane.

Have you checked the parameters that your IDE passes to Corona?

Given that you are the only person complaining that ZeroBrane does not work nicely with Corona perhaps it is your setup and not everyone else’s.

Being a software tester, why should Corona consider a use case outside their control?

#13

I didn’t change the setup and it broke after some new skins are introduced in the Corona build

And I have two Mac computers, both was working fine and suddenly Corona couldn’t remember last position.

I don’t think it’s a setup problem.

If there is extra setup I have to add, I hope Corona can teach me (or where should I find it out?)

#14

@joe528, try closing the simulator after you move it without using “Stop” in ZBS. ZBS will detect that the application is closed and will stop the debugging, but it may give the Simulator a chance to save its new position. I’m not sure what changed in the recent Corona SDK build, but see if this helps. Paul.

#15

@paulclinger

That will work. Thanks.

But hope either Corona or ZBS can correct this somehow, or I have to remember to close it without using stop when I want the last position to be remembered.

#16

After the last thread, somehow it started working well even if I use “Stop” in ZBS.  I am not sure who fixed this. My guess is Corona. There is nothing ZBS can do for this.

However, after 6 or 7 months, with recent Corona builds, this issue is happening again.

I cannot use the Stop in ZBS if I want the simulator to remember its last position. Corona must have changed something and break this again.

It becomes very inconvenient and hope Corona can take a look. 

#17

@joe528, I’ll check with my contacts, but what version of the Simulator are you using?

#18

@paulclinger

Corona 2702

but I am using ZBS 1.0 instead of 1.1

#19

This has to do with the way Zerobrane Studio terminates the Corona Simulator.  It seems like this worked before purely by chance and some rearrangement of the internals of the Simulator changed things enough that it doesn’t work in the desired manner anymore.  In the short term, Paul’s suggestion to set the window position and quit the Corona Simulator via it’s “Quit” menu item should cause the window position to be remembered and then you can use ZBS’s “Stop” function and the remembered window position should be used from then on (I haven’t tried this but I would expect it to work).

In the longer term, Paul and I will see what we can do to make the interaction more reliable. 

#20

Yes, using “Quit” via Simulator will work.

However, it is very inconvenient. I still use Stop most of the times & whenever I find I should use Quit, I sign.

I don’t need fancy features from an editor, but this is a basic integration (above all, it was working!)